Devices and Methods for Processing Touch Inputs

ABSTRACT

An electronic device with a touch-sensitive surface displays a user interface of a first software application that is updated at a first display rate. While displaying a first frame of the user interface in accordance with the first display rate, the device detects respective movement of a touch input across the touch-sensitive surface. An application-independent touch processing module of the device selects a respective touch location of the touch input that was detected during the respective movement to identify as a representative touch location for the respective movement based on touch-processing criteria for the first software application, and sends to an application-specific portion of the first software application touch location information for the touch input that identifies the respective touch location as the representative touch location for the respective movement. The first software application updates the user interface in accordance with the touch location information.

RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 16/179,813, filed Nov. 2, 2018, which is a continuation of U.S.patent application Ser. No. 14/871,415, filed Sep. 30, 2015, now U.S.Pat. No. 10,241,599, which is a continuation application of U.S. patentapplication Ser. No. 14/870,879, filed Sep. 30, 2015, now U.S. Pat. No.10,126,847, which claims priority to U.S. Provisional Patent ApplicationSer. No. 62/172,222, filed Jun. 7, 2015. All of these applications areincorporated by reference herein in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that receive touch inputs.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But rapid movements of touch inputs lead to discrepancies between actuallocations of touch inputs and how the touch inputs are reflected in userinterfaces. For example, the user interfaces may be updated with a delayso that they may not timely reflect locations of the touch inputs whentouch inputs are moving fast. This creates a cognitive burden on a user.In addition, this may lead to errors in manipulating user interfaceobjects and require repeated corrections, thereby wasting energy. Thislatter consideration is particularly important in battery-operateddevices.

SUMMARY

Accordingly, the present disclosure provides for electronic devices withfaster, more efficient and accurate methods and interfaces formanipulating user interface objects. Such methods and interfacesoptionally complement or replace conventional methods for manipulatinguser interface objects. Such methods and interfaces reduce the number,extent, and/or nature of the inputs from a user and produce a moreefficient human-machine interface. Further, such methods reduce theprocessing power consumed to process touch inputs, conserve power,improve accuracy of user inputs, reduceunnecessary/extraneous/repetitive inputs, and potentially reduce memoryusage. For battery-operated devices, such methods and interfacesconserve battery power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors. Alternatively, or inaddition, executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. In someembodiments, the electronic device includes one or more sensors todetect intensity of contacts with the touch-sensitive surface. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device. Themethod includes: displaying a user interface at a first display rate;while displaying the user interface, detecting, at a first detectionrate that is greater than the first display rate, movement of a touchinput at a sequence of locations on the touch-sensitive surface; and, ateach of a sequence of update times, updating the user interface from arespective current state to a respective next state in accordance with aselected subset of the sequence of locations of the touch input, eachselected subset of the sequence of locations comprising a plurality oflocations of the touch input.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. In someembodiments, the electronic device includes one or more sensors todetect intensity of contacts with the touch-sensitive surface. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device. Themethod includes: displaying a user interface of a first softwareapplication that is updated at a first display rate; and whiledisplaying a first frame of the user interface in accordance with thefirst display rate: detecting respective movement of a touch inputacross the touch-sensitive surface; and, at an application-independenttouch processing module: selecting a respective touch location of thetouch input that was detected during the respective movement to identifyas a representative touch location for the respective movement based ontouch-processing criteria for the first software application; andsending to an application-specific portion of the first softwareapplication, which is distinct from the touch processing module, touchlocation information for the touch input that identifies the respectivetouch location as the representative touch location for the respectivemovement. The method also includes, at the first software application,updating the user interface in accordance with the touch locationinformation.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. In someembodiments, the electronic device includes one or more sensors todetect intensity of contacts with the touch-sensitive surface. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device. Themethod includes: displaying a user interface at a first display rate;and, while displaying the user interface in accordance with the firstdisplay rate, detecting movement of a touch input, including detectingthe touch input at a first set of sequential locations on thetouch-sensitive surface. The first set of sequential locations includesa plurality of locations on the touch-sensitive surface. The method alsoincludes predicting for the touch input a first set of one or morepredicted locations on the touch-sensitive surface based on multiplelocations in the first set of sequential locations. The method furtherincludes updating the user interface in accordance with the first set ofone or more predicted locations of the touch input on thetouch-sensitive surface.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. In someembodiments, the electronic device includes one or more sensors todetect intensity of contacts with the touch-sensitive surface. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device. Themethod includes: displaying a user interface of a first softwareapplication that is updated at a first display rate; and detectingrespective movement of a touch input across the touch-sensitive surfaceat a first detection rate that is higher than the first display rate.The method also includes, at an application-independent touch processingmodule, sending to an application-specific portion of the first softwareapplication touch location information for the touch input thatidentifies: one or more predicted locations of the touch input on thetouch-sensitive surface; and one or more predicted intensity values ofthe touch input at one or more intensity locations of the touch input onthe touch-sensitive surface, the one or more intensity locationscomprising at least a subset of the one or more predicted locations. Themethod further includes, at the first software application, processingthe touch location information.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, and a processing unit coupled with thedisplay unit and the touch-sensitive surface unit. The processing unitis configured to: enable display of a user interface at a first displayrate; while the user interface is displayed, detect, at a firstdetection rate that is greater than the first display rate, movement ofa touch input at a sequence of locations on the touch-sensitive surfaceunit; and, at each of a sequence of update times, update the userinterface from a respective current state to a respective next state inaccordance with a selected subset of the sequence of locations of thetouch input, each selected subset of the sequence of locationscomprising a plurality of locations of the touch input. In someembodiments, the electronic device includes one or more sensor units todetect intensity of contacts with the touch-sensitive surface and theprocessing unit is coupled with the one or more sensor units. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device andthe processing unit is coupled with the one or more sensor units.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, and a processing unit coupled with thedisplay unit and the touch-sensitive surface unit. The processing unitis configured to: enable display of a user interface of a first softwareapplication that is updated at a first display rate; while a first frameof the user interface in accordance with the first display rate isdisplayed: detect respective movement of a touch input across thetouch-sensitive surface unit; and, at an application-independent touchprocessing module: select a respective touch location of the touch inputthat was detected during the respective movement to identify as arepresentative touch location for the respective movement based ontouch-processing criteria for the first software application; and sendto an application-specific portion of the first software application,which is distinct from the touch processing module, touch locationinformation for the touch input that identifies the respective touchlocation as the representative touch location for the respectivemovement; and, at the first software application, update the userinterface in accordance with the touch location information. In someembodiments, the electronic device includes one or more sensor units todetect intensity of contacts with the touch-sensitive surface and theprocessing unit is coupled with the one or more sensor units. In someembodiments, the electronic device includes one or more sensor units todetect signals from a stylus associated with the electronic device andthe processing unit is coupled with the one or more sensor units.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, and a processing unit coupled with thedisplay unit and the touch-sensitive surface unit. The processing unitis configured to: enable display of a user interface at a first displayrate; while displaying the user interface in accordance with the firstdisplay rate: detect movement of a touch input, including detecting thetouch input at a first set of sequential locations on thetouch-sensitive surface unit, wherein the first set of sequentiallocations includes a plurality of locations on the touch-sensitivesurface unit; and predict for the touch input a first set of one or morepredicted locations on the touch-sensitive surface unit based onmultiple locations in the first set of sequential locations; and updatethe user interface in accordance with the first set of one or morepredicted locations of the touch input on the touch-sensitive surfaceunit. In some embodiments, the electronic device includes one or moresensor units to detect intensity of contacts with the touch-sensitivesurface and the processing unit is coupled with the one or more sensorunits. In some embodiments, the electronic device includes one or moresensor units to detect signals from a stylus associated with theelectronic device and the processing unit is coupled with the one ormore sensor units.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, a touch-sensitivesurface unit to receive contacts, and a processing unit coupled with thedisplay unit and the touch-sensitive surface unit. The processing unitis configured to: enable display of a user interface of a first softwareapplication that is updated at a first display rate; detect respectivemovement of a touch input across the touch-sensitive surface unit at afirst detection rate that is higher than the first display rate; at anapplication-independent touch processing module, send to anapplication-specific portion of the first software application touchlocation information for the touch input that identifies: one or morepredicted locations of the touch input on the touch-sensitive surfaceunit; and one or more predicted intensity values of the touch input atone or more intensity locations of the touch input on thetouch-sensitive surface unit, the one or more intensity locationscomprising at least a subset of the one or more predicted locations;and, at the first software application, process the touch locationinformation. In some embodiments, the electronic device includes one ormore sensor units to detect intensity of contacts with thetouch-sensitive surface and the processing unit is coupled with the oneor more sensor units. In some embodiments, the electronic deviceincludes one or more sensor units to detect signals from a stylusassociated with the electronic device and the processing unit is coupledwith the one or more sensor units.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, one or more processors, memory, oneor more programs, optionally one or more sensors to detect intensity ofcontacts with the touch-sensitive surface, and optionally one or moresensors to detect signals from a stylus associated with the electronicdevice; the one or more programs are stored in the memory and configuredto be executed by the one or more processors and the one or moreprograms include instructions for performing or causing performance ofthe operations of any of the methods described herein. In accordancewith some embodiments, a computer readable storage medium (e.g., anon-transitory computer readable storage medium, or alternatively, atransitory computer readable storage medium) has stored thereininstructions, which, when executed by an electronic device with adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, andoptionally one or more sensors to detect signals from a stylusassociated with the electronic device, cause the electronic device toperform or cause performance of the operations of any of the methodsdescribed herein. In accordance with some embodiments, a graphical userinterface on an electronic device with a display, a touch-sensitivesurface, a memory, one or more processors to execute one or moreprograms stored in the memory, optionally one or more sensors to detectintensity of contacts with the touch-sensitive surface, and optionallyone or more sensors to detect signals from a stylus associated with theelectronic device, includes one or more of the elements displayed in anyof the methods described herein, which are updated in response toinputs, as described in any of the methods described herein. Inaccordance with some embodiments, an electronic device includes: adisplay, a touch-sensitive surface, and means for performing or causingperformance of the operations of any of the methods described herein.The electronic device optionally includes one or more sensors to detectsignals from a stylus associated with the electronic device and/or oneor more sensors to detect intensity of contacts with the touch-sensitivesurface. In accordance with some embodiments, an information processingapparatus, for use in an electronic device with a display and atouch-sensitive surface, includes means for performing or causingperformance of the operations of any of the methods described herein.The electronic device optionally includes one or more sensors to detectsignals from a stylus associated with the electronic device and/or oneor more sensors to detect intensity of contacts with the touch-sensitivesurface.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, and optionally one or more sensors to detectsignals from a stylus associated with the electronic device are providedwith faster, more efficient methods and interfaces for manipulating userinterface objects, thereby increasing the effectiveness, efficiency, anduser satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for manipulating userinterface objects.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 1C is a block diagram illustrating transfer of an event object inaccordance with some embodiments.

FIG. 1D is a block diagram illustrating a structure of an event objectin accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4 is a block diagram of an exemplary electronic stylus inaccordance with some embodiments.

FIGS. 5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface in accordance with some embodiments.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 6B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 7A-7OO illustrate exemplary user interfaces for updating a userinterface based on coalesced and/or predicted touch locations andrelated operations in accordance with some embodiments.

FIGS. 8A-8B are flow diagrams illustrating a method of updating a userinterface based on coalesced touch locations in accordance with someembodiments.

FIGS. 9A-9D are flow diagrams illustrating a method of processing atouch input with a touch processing module in accordance with someembodiments.

FIGS. 10A-10C are flow diagrams illustrating a method of updating a userinterface based on predicted touch locations in accordance with someembodiments.

FIG. 11 is a flow diagram illustrating a method of transferringpredicted touch information in accordance with some embodiments.

FIGS. 12-15 are functional block diagrams of an electronic device inaccordance with some embodiments.

Drawings are not drawn to scale unless stated otherwise.

DESCRIPTION OF EMBODIMENTS

Many electronic devices have graphical user interfaces receive userinputs to manipulate user interface objects (e.g., moving a userinterface object or creating a user interface object, such as drawing aline). Due to delays associated with hardware and/or software componentsin processing touch inputs, rapid movements of touch inputs lead todiscrepancies between actual locations of touch inputs and how the touchinputs are reflected in user interfaces. For example, the userinterfaces may be updated with a delay so that they may not timelyreflect locations of the touch inputs when touch inputs are moving fast.This creates a cognitive burden on a user, and may lead to errors inmanipulating user interface objects. In the embodiments described below,an improved method for manipulating user interface objects is achievedby using coalesced touch locations, predicted touch locations, or thecombination of both coalesced touch locations and predicted touchlocations. By detecting a touch input at a higher rate (e.g., higherthan a display rate), locations of the touch input can be detectedbetween frames. This location information is used to reduce thediscrepancy. In addition, or alternatively, locations of the touch inputare predicted, which is also used to reduce the discrepancy. This methodstreamlines the object manipulation processes by using coalesced and/orpredicted touch locations, thereby reducing discrepancies between touchinputs and displayed user interfaces and allowing more accuratemanipulation of user interface objects.

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIG. 4 provides a description of an exemplary electronic stylus. FIGS.5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface. FIGS. 6A-6B and 7A-7OO illustrate exemplaryuser interfaces for updating a user interface based on coalesced and/orpredicted touch locations and related operations. FIGS. 8A-8B illustratea flow diagram of a method of updating a user interface based oncoalesced touch locations. FIGS. 9A-9D illustrate a flow diagram of amethod of processing a touch input with a touch processing module. FIGS.10A-10C illustrate a flow diagram of a method of updating a userinterface based on predicted touch locations. FIG. 11 illustrates a flowdiagram of a method of transferring predicted touch information. Theuser interfaces in FIGS. 7A-7OO are used to illustrate the processes inFIGS. 8A-8B, 9A-9D, 10A-10C, and 11.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In some exemplary embodiments, apoint of contact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In some exemplary embodiments, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). In some embodiments, tactile output generator(s) 163 receivetactile feedback generation instructions from haptic feedback module 133and generates tactile outputs on device 100 that are capable of beingsensed by a user of device 100. In some embodiments, at least onetactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touch-sensitive display system 112) and,optionally, generates a tactile output by moving the touch-sensitivesurface vertically (e.g., in/out of a surface of device 100) orlaterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensoris located on the back of device 100, opposite touch-sensitive displaysystem 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,position module (or set of instructions) 131, graphics module (or set ofinstructions) 132, haptic feedback module (or set of instructions) 133,text input module (or set of instructions) 134, Global PositioningSystem (GPS) module (or set of instructions) 135, and applications (orsets of instructions) 136. Furthermore, in some embodiments, memory 102stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch-sensitive display system112; sensor state, including information obtained from the device'svarious sensors and other input or control devices 116; and locationand/or positional information concerning the device's location and/orattitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Position module 131, in conjunction with accelerometers 167, gyroscopes168, and/or magnetometers 169, optionally detects positional informationconcerning the device, such as the device's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 130includes software components for performing various operations relatedto detecting the position of the device and detecting changes to theposition of the device. In some embodiments, position module 131 usesinformation received from a stylus being used with the device to detectpositional information concerning the stylus, such as detecting thepositional state of the stylus relative to the device and detectingchanges to the positional state of the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions (e.g., used by haptic feedback controller 161)to produce tactile output using tactile output generator(s) 163 at oneor more locations on device 100 in response to user interactions withdevice 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, a respective event definition 186 includes adefinition of an event for a respective user-interface object. In someembodiments, event comparator 184 performs a hit test to determine whichuser-interface object is associated with a sub-event. For example, in anapplication view in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 1C is a block diagram illustrating transfer of an event object(e.g., event object 194 in FIG. 1D) in accordance with some embodiments.

As described above with respect to FIG. 1A, contact/motion module 130determines status and/or a change in the status of a touch input. Insome embodiments, the device generates signal or data (e.g., in the formof a data object) to transfer the determined status and/or thedetermined change in the status of a touch input to one or more softwarecomponents. In some embodiments, the data object is called an eventobject (e.g., event object 194). An event object includes data thatrepresents the status of a corresponding touch input. In someembodiments, event object 194 is a mouse event object (e.g., an eventobject that includes information for one or more mouse events, such asmovement of a mouse, button clicks, etc.). In some other embodiments,event object 194 is a touch event object that is distinct from a mouseevent object. In some embodiments, the touch event object includes datathat represents touch-specific properties of a corresponding touch input(e.g., a number of concurrent touches, an orientation of a fingercontact or a stylus, etc.). In some embodiments, event object 194includes data that represents force event specific properties of acorresponding touch input (e.g., an intensity applied by the touchinput, a force stage/phase of the touch input, etc.). For example, amouse event object that includes information for one or more forceevents (e.g., an intensity applied by the touch input, a forcestage/phase of the touch input, etc.) may be used.

In some embodiments, contact/motion module 130 generates (or updates) anevent object and sends an event object to one or more applications(e.g., application 136-1, such as drawing module 380 in FIG. 3, and/orapplication 136-2, such as browser module 147). Alternatively,contact/information module 130 sends information regarding contacts(e.g., raw coordinates of contacts) to one or more applications (e.g.,application 1 (136-1) and/or application 2 (136-2)), and an applicationthat receives the information generates (or updates) one or more eventobjects. In some embodiments, an application includes touch-processingmodule 220 that generates (or updates) one or more event objects andsends the one or more event objects to a portion of the applicationother than touch-processing module 220. In some embodiments,touch-processing module 220 is application-independent (e.g., the sametouch-processing module is included in each of multiple distinctapplications, such as drawing application, browser application, etc.).As used herein, that touch-processing module 220 isapplication-independent means that touch-processing module 220 is notdesigned specifically for a particular software application. Thattouch-processing module 220 is application-independent does not meanthat touch-processing module 220 is located separate from its associatedapplication. Although touch-processing module 220, in some embodiments,is distinct and separate from its associated application, as shown inFIG. 1C, touch-processing module 220 is included in its associatedapplication in some embodiments. In some embodiments, the applicationalso includes an application core that is specific to the application.

In FIG. 1C, each of application 1 (136-1, such as a drawing application)and application 2 (136-2, such as a browser application) includes touchprocessing module 220. In addition, application 1 (136-1) includesapplication core 1 (230-1) that is specific to application 1 (136-1)and/or application 2 (136-2) includes application core 2 (230-2) that isspecific to application 2 (136-2). For example, application core 1(230-1) includes instructions for performing operations specific toapplication 1 (136-1) (e.g., drawing pen strokes) and application core 2(230-2) includes instructions for performing operations specific toapplication 2 (136-2) (e.g., bookmarking a web page).

In some embodiments, event object 194 is sent directly to thedestination (e.g., a software component, such as application core 1(230-1)). Optionally, event object 194 is sent through applicationprogramming interface 222. In some embodiments, event object 194 is sentby posting event object 194 (e.g., in queue 218-1) for retrieval byapplication core 1 (230-1).

In some embodiments, event object 194 includes force information. Insome embodiments, a mouse event object includes force information (e.g.,raw or normalized force applied by the touch input). In someembodiments, a touch event object includes force information. In someembodiments, a force event object includes force information.

FIG. 1D is a block diagram illustrating a structure of event object 194in accordance with some embodiments.

Event object 194 includes detected touch information 242 thatcorresponds to one or more detected touches. In some embodiments,detected touch information 242 includes information for separatedetected touches (e.g., information 246-1 for touch 1, information 246-2for touch 2, etc.). Detected touch information 242 optionally includes atouch identifier (e.g., touch identifier 1 (246-1) for touch 1, touchidentifier 2 (246-2) for touch 2, etc.). In some embodiments, detectedtouch information 242 includes information that identifiesrepresentative touches (e.g., touch identifiers of representativetouches).

Information for a separate touch includes location information 250 of acorresponding touch, and optionally, information 252 that identifies anintensity applied by the corresponding touch, information 254 thatidentifies tilt and/or orientation of a stylus associated with thedevice, timestamp 256 of the corresponding touch (e.g., timestamp 26indicates time when the corresponding touch was detected), and/or type258 of the corresponding touch (e.g., whether the corresponding touch ismade with a finger or a stylus). In some embodiments, the values forsome of these fields are predicted, even for detected touches (e.g., theforce and/or tilt values for a detected touch are predicted due tolatency in acquiring force and/or tilt information about the touch).

In some embodiments, event object 194 also includes predicted touchinformation 244 that corresponds to one or more predicted touches. Thestructure of predicted touch information 244 is similar to the structureof detected touch information 242 described above. For brevity, suchdetails are not repeated herein.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In these embodiments, as wellas others described below, a user is enabled to select one or more ofthe graphics by making a gesture on the graphics, for example, with oneor more fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 164,165, 166, 167, 168, and 169 described above with reference to FIG. 1A).Memory 370 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

FIG. 4 is a block diagram of an exemplary electronic stylus 203 inaccordance with some embodiments. Electronic stylus 203 is sometimessimply called a stylus. Stylus 203 includes memory 402 (which optionallyincludes one or more computer readable storage mediums), memorycontroller 422, one or more processing units (CPUs) 420, peripheralsinterface 418, RF circuitry 408, input/output (I/O) subsystem 406, andother input or control devices 416. Stylus 203 optionally includesexternal port 424 and one or more optical sensors 464. Stylus 203optionally includes one or more intensity sensors 465 for detectingintensity of contacts of stylus 203 on device 100 (e.g., when stylus 203is used with a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100) or on other surfaces (e.g., a desk surface).Stylus 203 optionally includes one or more tactile output generators 463for generating tactile outputs on stylus 203. These componentsoptionally communicate over one or more communication buses or signallines 403.

In some embodiments, the term “tactile output,” discussed above, refersto physical displacement of an accessory (e.g., stylus 203) of a device(e.g., device 100) relative to a previous position of the accessory,physical displacement of a component of an accessory relative to anothercomponent of the accessory, or displacement of the component relative toa center of mass of the accessory that will be detected by a user withthe user's sense of touch. For example, in situations where theaccessory or the component of the accessory is in contact with a surfaceof a user that is sensitive to touch (e.g., a finger, palm, or otherpart of a user's hand), the tactile output generated by the physicaldisplacement will be interpreted by the user as a tactile sensationcorresponding to a perceived change in physical characteristics of theaccessory or the component of the accessory. For example, movement of acomponent (e.g., the housing of stylus 203) is, optionally, interpretedby the user as a “click” of a physical actuator button. In some cases, auser will feel a tactile sensation such as a “click” even when there isno movement of a physical actuator button associated with the stylusthat is physically pressed (e.g., displaced) by the user's movements.While such interpretations of touch by a user will be subject to theindividualized sensory perceptions of the user, there are many sensoryperceptions of touch that are common to a large majority of users. Thus,when a tactile output is described as corresponding to a particularsensory perception of a user (e.g., a “click,”), unless otherwisestated, the generated tactile output corresponds to physicaldisplacement of the device or a component thereof that will generate thedescribed sensory perception for a typical (or average) user.

It should be appreciated that stylus 203 is only one example of anelectronic stylus, and that stylus 203 optionally has more or fewercomponents than shown, optionally combines two or more components, oroptionally has a different configuration or arrangement of thecomponents. The various components shown in FIG. 4 are implemented inhardware, software, firmware, or a combination thereof, including one ormore signal processing and/or application specific integrated circuits.

Memory 402 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or more flashmemory devices, or other non-volatile solid-state memory devices. Accessto memory 402 by other components of stylus 203, such as CPU(s) 420 andthe peripherals interface 418, is, optionally, controlled by memorycontroller 422.

Peripherals interface 418 can be used to couple input and outputperipherals of the stylus to CPU(s) 420 and memory 402. The one or moreprocessors 420 run or execute various software programs and/or sets ofinstructions stored in memory 402 to perform various functions forstylus 203 and to process data.

In some embodiments, peripherals interface 418, CPU(s) 420, and memorycontroller 422 are, optionally, implemented on a single chip, such aschip 404. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 408 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 408 converts electricalsignals to/from electromagnetic signals and communicates with device 100or 300, communications networks, and/or other communications devices viathe electromagnetic signals. RF circuitry 408 optionally includeswell-known circuitry for performing these functions, including but notlimited to an antenna system, an RF transceiver, one or more amplifiers,a tuner, one or more oscillators, a digital signal processor, a CODECchipset, a subscriber identity module (SIM) card, memory, and so forth.RF circuitry 408 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

I/O subsystem 406 couples input/output peripherals on stylus 203, suchas other input or control devices 416, with peripherals interface 418.I/O subsystem 406 optionally includes optical sensor controller 458,intensity sensor controller 459, haptic feedback controller 461, and oneor more input controllers 460 for other input or control devices. Theone or more input controllers 460 receive/send electrical signalsfrom/to other input or control devices 416. The other input or controldevices 416 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, click wheels, and soforth. In some alternate embodiments, input controller(s) 460 are,optionally, coupled with any (or none) of the following: an infraredport and/or a USB port.

Stylus 203 also includes power system 462 for powering the variouscomponents. Power system 462 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices and/or portableaccessories.

Stylus 203 optionally also includes one or more optical sensors 464.FIG. 4 shows an optical sensor coupled with optical sensor controller458 in I/O subsystem 406. Optical sensor(s) 464 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 464 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image.

Stylus 203 optionally also includes one or more contact intensitysensors 465. FIG. 4 shows a contact intensity sensor coupled withintensity sensor controller 459 in I/O subsystem 406. Contact intensitysensor(s) 465 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a surface). Contact intensitysensor(s) 465 receive contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a tip of stylus 203.

Stylus 203 optionally also includes one or more proximity sensors 466.FIG. 4 shows proximity sensor 466 coupled with peripherals interface418. Alternately, proximity sensor 466 is coupled with input controller460 in I/O subsystem 406. In some embodiments, the proximity sensordetermines proximity of stylus 203 to an electronic device (e.g., device100).

Stylus 203 optionally also includes one or more tactile outputgenerators 463. FIG. 4 shows a tactile output generator coupled withhaptic feedback controller 461 in I/O subsystem 406. Tactile outputgenerator(s) 463 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 463 receive tactile feedbackgeneration instructions from haptic feedback module 433 and generatestactile outputs on stylus 203 that are capable of being sensed by a userof stylus 203. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a length (e.g., a body ora housing) of stylus 203 and, optionally, generates a tactile output bymoving stylus 203 vertically (e.g., in a direction parallel to thelength of stylus 203) or laterally (e.g., in a direction normal to thelength of stylus 203).

Stylus 203 optionally also includes one or more accelerometers 467,gyroscopes 468, and/or magnetometers 470 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning thelocation and positional state of stylus 203. FIG. 4 shows sensors 467,469, and 470 coupled with peripherals interface 418. Alternately,sensors 467, 469, and 470 are, optionally, coupled with an inputcontroller 460 in I/O subsystem 406. Stylus 203 optionally includes aGPS (or GLONASS or other global navigation system) receiver (not shown)for obtaining information concerning the location of stylus 203.

In some embodiments, the software components stored in memory 402include operating system 426, communication module (or set ofinstructions) 428, contact/motion module (or set of instructions) 430,position module (or set of instructions) 431, and Global PositioningSystem (GPS) module (or set of instructions) 435. Furthermore, in someembodiments, memory 402 stores device/global internal state 457, asshown in FIG. 4. Device/global internal state 457 includes one or moreof: sensor state, including information obtained from the stylus'svarious sensors and other input or control devices 416; positionalstate, including information regarding the stylus's position (e.g.,position, orientation, tilt, roll and/or distance, as shown in FIGS. 5Aand 5B) relative to a device (e.g., device 100); and locationinformation concerning the stylus's location (e.g., determined by GPSmodule 435).

Operating system 426 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, power management, etc.)and facilitates communication between various hardware and softwarecomponents.

Communication module 428 optionally facilitates communication with otherdevices over one or more external ports 424 and also includes varioussoftware components for handling data received by RF circuitry 408and/or external port 424. External port 424 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a Lightning connector that isthe same as, or similar to and/or compatible with the Lightningconnector used in some iPhone®, iPod Touch®, and iPad® devices fromApple Inc. of Cupertino, Calif.

Contact/motion module 430 optionally detects contact with stylus 203 andother touch-sensitive devices of stylus 203 (e.g., buttons or othertouch-sensitive components of stylus 203). Contact/motion module 430includes software components for performing various operations relatedto detection of contact (e.g., detection of a tip of the stylus with atouch-sensitive display, such as touch screen 112 of device 100, or withanother surface, such as a desk surface), such as determining if contacthas occurred (e.g., detecting a touch-down event), determining anintensity of the contact (e.g., the force or pressure of the contact ora substitute for the force or pressure of the contact), determining ifthere is movement of the contact and tracking the movement (e.g., acrosstouch screen 112 of device 100), and determining if the contact hasceased (e.g., detecting a lift-off event or a break in contact). In someembodiments, contact/motion module 430 receives contact data from I/Osubsystem 406. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. As noted above, in some embodiments, one or more of theseoperations related to detection of contact are performed by the deviceusing contact/motion module 130 (in addition to or in place of thestylus using contact/motion module 430).

Contact/motion module 430 optionally detects a gesture input by stylus203. Different gestures with stylus 203 have different contact patterns(e.g., different motions, timings, and/or intensities of detectedcontacts). Thus, a gesture is, optionally, detected by detecting aparticular contact pattern. For example, detecting a single tap gestureincludes detecting a touch-down event followed by detecting a lift-offevent at the same position (or substantially the same position) as thetouch-down event (e.g., at the position of an icon). As another example,detecting a swipe gesture includes detecting a touch-down event followedby detecting one or more stylus-dragging events, and subsequentlyfollowed by detecting a lift-off event. As noted above, in someembodiments, gesture detection is performed by the device usingcontact/motion module 130 (in addition to or in place of the stylususing contact/motion module 430).

Position module 431, in conjunction with accelerometers 467, gyroscopes468, and/or magnetometers 469, optionally detects positional informationconcerning the stylus, such as the stylus's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 431, inconjunction with accelerometers 467, gyroscopes 468, and/ormagnetometers 469, optionally detects stylus movement gestures, such asflicks, taps, and rolls of the stylus. Position module 431 includessoftware components for performing various operations related todetecting the position of the stylus and detecting changes to theposition of the stylus in a particular frame of reference. In someembodiments, position module 431 detects the positional state of thestylus relative to the device and detects changes to the positionalstate of the stylus relative to the device. As noted above, in someembodiments, device 100 or 300 determines the positional state of thestylus relative to the device and changes to the positional state of thestylus using position module 131 (in addition to or in place of thestylus using position module 431).

Haptic feedback module 433 includes various software components forgenerating instructions used by tactile output generator(s) 463 toproduce tactile outputs at one or more locations on stylus 203 inresponse to user interactions with stylus 203.

GPS module 435 determines the location of the stylus and provides thisinformation for use in various applications (e.g., to applications thatprovide location-based services such as an application to find missingdevices and/or accessories).

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 402 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 402 optionally stores additionalmodules and data structures not described above.

FIGS. 5A-5B illustrate a positional state of stylus 203 relative to atouch-sensitive surface (e.g., touch screen 112 of device 100) inaccordance with some embodiments. In some embodiments, the positionalstate of stylus 203 corresponds to (or indicates): a position of aprojection of a tip (or other representative portion) of the stylus onthe touch-sensitive surface (e.g., (x,y) position 504, FIG. 5A), anorientation of the stylus relative to the touch-sensitive surface (e.g.,orientation 506, FIG. 5A), a tilt of the stylus relative to thetouch-sensitive surface (e.g., tilt 512, FIG. 5B), and/or a distance ofthe stylus relative to the touch-sensitive surface (e.g., distance 514,FIG. 5B). In some embodiments, the positional state of stylus 203corresponds to (or indicates) a pitch, yaw, and/or roll of the stylus(e.g., an attitude of the stylus relative to a particular frame ofreference, such as a touch-sensitive surface (e.g., touch screen 112) orthe ground). In some embodiments, the positional state includes a set ofpositional parameters (e.g., one or more positional parameters). In someembodiments, the positional state is detected in accordance with one ormore measurements from stylus 203 that are sent to an electronic device(e.g., device 100). For example, the stylus measures the tilt (e.g.,tilt 512, FIG. 5B) and/or the orientation (e.g., orientation 506, FIG.5A) of the stylus and sends the measurement to device 100. In someembodiments, the positional state is detected in accordance with rawoutput, from one or more electrodes in the stylus, that is sensed by atouch-sensitive surface (e.g., touch screen 112 of device 100) insteadof, or in combination with positional state detected in accordance withone or more measurements from stylus 203. For example, thetouch-sensitive surface receives raw output from one or more electrodesin the stylus and calculates the tilt and/or the orientation of thestylus based on the raw output (optionally, in conjunction withpositional state information provided by the stylus based on sensormeasurements generated by the stylus).

FIG. 5A illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a viewpoint directly abovethe touch-sensitive surface, in accordance with some embodiments. InFIG. 5A, z axis 594 points out of the page (i.e., in a direction normalto a plane of touch screen 112), x axis 590 is parallel to a first edge(e.g., a length) of touch screen 112, y axis 592 is parallel to a secondedge (e.g., a width) of touch screen 112, and y axis 592 isperpendicular to x axis 590.

FIG. 5A illustrates the tip of stylus 203 at (x,y) position 504. In someembodiments, the tip of stylus 203 is a terminus of the stylusconfigured for determining proximity of the stylus to a touch-sensitivesurface (e.g., touch screen 112). In some embodiments, the projection ofthe tip of the stylus on the touch-sensitive surface is an orthogonalprojection. In other words, the projection of the tip of the stylus onthe touch-sensitive surface is a point at the end of a line from thestylus tip to the touch-sensitive surface that is normal to a surface ofthe touch-sensitive surface (e.g., (x,y) position 504 at which the tipof the stylus would touch the touch-sensitive surface if the stylus weremoved directly along a path normal to the touch-sensitive surface). Insome embodiments, the (x,y) position at the lower left corner of touchscreen 112 is position (0,0) (e.g., (0,0) position 502) and other (x,y)positions on touch screen 112 are relative to the lower left corner oftouch screen 112. Alternatively, in some embodiments, the (0,0) positionis located at another position of touch screen 112 (e.g., in the centerof touch screen 112) and other (x,y) positions are relative to the (0,0)position of touch screen 112.

Further, FIG. 5A illustrates stylus 203 with orientation 506. In someembodiments, orientation 506 is an orientation of a projection of stylus203 onto touch screen 112 (e.g., an orthogonal projection of a length ofstylus 203 or a line corresponding to the line between the projection oftwo different points of stylus 203 onto touch screen 112). In someembodiments, orientation 506 is relative to at least one axis in a planeparallel to touch screen 112. In some embodiments, orientation 506 isrelative to a single axis in a plane parallel to touch screen 112 (e.g.,axis 508, with a clockwise rotation angle from axis 508 ranging from 0degrees to 360 degrees, as shown in FIG. 5A). Alternatively, in someembodiments, orientation 506 is relative to a pair of axes in a planeparallel to touch screen 112 (e.g., x axis 590 and y axis 592, as shownin FIG. 5A, or a pair of axes associated with an application displayedon touch screen 112).

In some embodiments, an indication (e.g., indication 516) is displayedon a touch-sensitive display (e.g., touch screen 112 of device 100). Insome embodiments, indication 516 shows where the stylus will touch (ormark) the touch-sensitive display before the stylus touches thetouch-sensitive display. In some embodiments, indication 516 is aportion of a mark that is being drawn on the touch-sensitive display. Insome embodiments, indication 516 is separate from a mark that is beingdrawn on the touch-sensitive display and corresponds to a virtual “pentip” or other element that indicates where a mark will be drawn on thetouch-sensitive display.

In some embodiments, indication 516 is displayed in accordance with thepositional state of stylus 203. For example, in some circumstances,indication 516 is displaced from (x,y) position 504 (as shown in FIGS.5A and 5B), and in other circumstances, indication 516 is not displacedfrom (x,y) position 504 (e.g., indication 516 is displayed at or near(x,y) position 504 when tilt 512 is zero degrees). In some embodiments,indication 516 is displayed, in accordance with the positional state ofthe stylus, with varying color, size (or radius or area), opacity,and/or other characteristics. In some embodiments, the displayedindication accounts for thickness of a glass layer on thetouch-sensitive display, so as to carry through the indication “onto thepixels” of the touch-sensitive display, rather than displaying theindication “on the glass” that covers the pixels.

FIG. 5B illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a side viewpoint of thetouch-sensitive surface, in accordance with some embodiments. In FIG.5B, z axis 594 points in a direction normal to the plane of touch screen112, x axis 590 is parallel to a first edge (e.g., a length) of touchscreen 112, y axis 592 is parallel to a second edge (e.g., a width) oftouch screen 112, and y axis 592 is perpendicular to x axis 590.

FIG. 5B illustrates stylus 203 with tilt 512. In some embodiments, tilt512 is an angle relative to a normal (e.g., normal 510) to a surface ofthe touch-sensitive surface (also called simply the normal to thetouch-sensitive surface). As shown in FIG. 5B, tilt 512 is zero when thestylus is perpendicular/normal to the touch-sensitive surface (e.g.,when stylus 203 is parallel to normal 510) and the tilt increases as thestylus is tilted closer to being parallel to the touch-sensitivesurface.

Further, FIG. 5B illustrates distance 514 of stylus 203 relative to thetouch-sensitive surface. In some embodiments, distance 514 is thedistance from the tip of stylus 203 to the touch-sensitive surface, in adirection normal to the touch-sensitive surface. For example, in FIG.5B, distance 514 is the distance from the tip of stylus 203 to (x,y)position 504.

Although the terms, “x axis,” “y axis,” and “z axis,” are used herein toillustrate certain directions in particular figures, it will beunderstood that these terms do not refer to absolute directions. Inother words, an “x axis” could be any respective axis, and a “y axis”could be a particular axis that is distinct from the x axis. Typically,the x axis is perpendicular to the y axis. Similarly, a “z axis” isdistinct from the “x axis” and the “y axis,” and is typicallyperpendicular to both the “x axis” and the “y axis.”

Further, FIG. 5B illustrates roll 518, a rotation about the length (longaxis) of stylus 203.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 600 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 602 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 604;    -   Bluetooth indicator 605;    -   Battery status indicator 606;    -   Tray 608 with icons for frequently used applications, such as:        -   Icon 616 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 614 of the number of missed            calls or voicemail messages;        -   Icon 618 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 610 of the number of unread            e-mails;        -   Icon 620 for browser module 147, labeled “Browser;” and        -   Icon 622 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 624 for IM module 141, labeled “Messages;”        -   Icon 626 for calendar module 148, labeled “Calendar;”        -   Icon 628 for image management module 144, labeled “Photos;”        -   Icon 630 for camera module 143, labeled “Camera;”        -   Icon 632 for online video module 155, labeled “Online            Video;”        -   Icon 634 for stocks widget 149-2, labeled “Stocks;”        -   Icon 636 for map module 154, labeled “Maps;”        -   Icon 638 for weather widget 149-1, labeled “Weather;”        -   Icon 640 for alarm clock widget 169-6, labeled “Clock;”        -   Icon 642 for workout support module 142, labeled “Workout            Support;”        -   Icon 644 for notes module 153, labeled “Notes;” and        -   Icon 646 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 6A aremerely exemplary. For example, in some embodiments, icon 622 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. Device300 also, optionally, includes one or more contact intensity sensors(e.g., one or more of sensors 359) for detecting intensity of contactson touch-sensitive surface 651 and/or one or more tactile outputgenerators 359 for generating tactile outputs for a user of device 300.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 6B. In some embodiments, the touch-sensitive surface (e.g., 651 inFIG. 6B) has a primary axis (e.g., 652 in FIG. 6B) that corresponds to aprimary axis (e.g., 653 in FIG. 6B) on the display (e.g., 650). Inaccordance with these embodiments, the device detects contacts (e.g.,660 and 662 in FIG. 6B) with the touch-sensitive surface 651 atlocations that correspond to respective locations on the display (e.g.,in FIG. 6B, 660 corresponds to 668 and 662 corresponds to 670). In thisway, user inputs (e.g., contacts 660 and 662, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 651 in FIG.6B) are used by the device to manipulate the user interface on thedisplay (e.g., 650 in FIG. 6B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact) or astylus contact followed by movement of the stylus along the path of theswipe. As another example, a tap gesture is, optionally, replaced with amouse click while the cursor is located over the location of the tapgesture (e.g., instead of detection of the contact followed by ceasingto detect the contact). Similarly, when multiple user inputs aresimultaneously detected, it should be understood that multiple stylusesare, optionally, used simultaneously, or finger and stylus contacts or amouse and finger contacts are, optionally, used simultaneously.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 and/or 430 uses a set ofone or more intensity thresholds to determine whether an operation hasbeen performed by a user (e.g., to determine whether a user has“clicked” on an icon). In some embodiments, at least a subset of theintensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of device 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined thresholds valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some embodiments, a user of the device is provided withsoftware settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures (e.g., FIGS. 7A-7OO) described belowoptionally include various intensity diagrams that show the currentintensity of the contact on the touch-sensitive surface relative to oneor more intensity thresholds (e.g., a contact detection intensitythreshold IT₀, a light press intensity threshold IT_(L), a deep pressintensity threshold IT_(D), and/or one or more other intensitythresholds). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector (e.g., a cursor) in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Exemplary factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface.

FIGS. 7A-7OO illustrate exemplary user interfaces for updating a userinterface based on coalesced and/or predicted touch locations inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 8A-8B, 9A-9D, 10A-10C, and 11. Although some of theexamples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs ontouch-sensitive surface 651 that is separate from display 650, as shownin FIG. 6B.

In some embodiments, display 650 is configured to display a userinterface at a particular display rate (also called a display refreshrate). For example, a particular monitor displays a user interface at 60Hz (e.g., at a rate of 60 updates every second). In some embodiments,the display rate is a fixed display rate. As used herein, a displayframe refers to a user interface that is displayed during a singledisplay cycle (e.g., a user interface that is displayed for ˜0.1667second when the display rate is 60 Hz, and subsequently replaced with asubsequent user interface).

In some embodiments, touch-sensitive surface 651 is configured to detecta touch input at a particular detection rate. In some embodiments, thedetection rate is a fixed detection rate (e.g., 60 Hz).

In some cases, there are delays between detecting a touch input andupdating a user interface in response to the touch input, such as delaysin processing the touch input and/or delays in preparing a userinterface (prior to rendering the user interface). Such delays can leadto a discrepancy between a physical location of a touch input on touchscreen 112 and updates to a user interface displayed on touch screen112. An example of which is illustrated in FIGS. 7A-7E.

FIG. 7A illustrates a user interface of a drawing application on touchscreen 112. In FIG. 7A, touch input 705 is detected at location 705-A ontouch screen 112. FIG. 7A also illustrates that, in response todetecting touch input 705, 702 dot is displayed on touch screen 112.

FIG. 7B illustrates that touch input 705 has moved across touch screen112 to location 705-B on touch screen 112. In FIG. 7B, line 704-1 isdisplayed in accordance with movement of touch input 705 from location705-A to location 705-B. However, due to delays in processing a touchinput, an end point of line 704-1 does not precisely match the locationof touch input 705 (e.g., location 705-B) while touch input 705 ismoving across touch screen 112.

FIG. 7B also includes a graph to describe this effect. In the graph ofFIG. 7B, movement of touch input 705 is represented by increasing traveldistances 740-1, 740-2, and 740-3 over time. In some embodiments, due todelays, when the travel distance is at 740-2, a user interface preparedbased on travel distance at 740-1 is displayed (750-1). Similarly, whenthe travel distance is at 740-3, travel distance 740-2 is used as length750-2 of line 704-1, and there is discrepancy d₁ between the actualtravel distance (e.g., 740-3) and the displayed length (e.g., 750-2) ofline 704-1 drawn in accordance with the touch input. In someembodiments, these travel distances correspond to travel distance duringa constant time interval (e.g., a single display-update frame, or theamount of time between when a touch is detected on the touch-sensitivesurface to when a display update that takes into account changes to theuser interface is generated in response to the touch), so that thedifferent distances correspond to different speeds (e.g., a largerchange in distance over a respective time interval corresponds to afaster movement of the contact across the touch-sensitive surface, whilea shorter change in distance over the respective time intervalcorresponds to a slower movement of the contact across thetouch-sensitive surface).

FIG. 7C illustrates continued movement of touch input 705 across touchscreen 112 to location 705-C. In the graph, when the travel distance isat 740-4, travel distance 740-3 is used as length 750-3 of line 704-2.

FIG. 7D illustrates faster movement of touch input 705 across touchscreen 112 to location 705-D. When the travel distance is at 740-6,travel distance 740-5 is used as length 750-5 of line 704-3, and thereis discrepancy d₂ between the actual travel distance (e.g., 740-6) andthe displayed length (e.g., 750-5) of line 704-3.

As shown in FIGS. 7B-7D, the discrepancy is relatively small when thetouch input moves across touch screen 112 at a slow speed, and thediscrepancy is less noticeable. However, the discrepancy increases withfaster movement of the touch input across touch screen 112, and thediscrepancy becomes more noticeable.

FIG. 7E illustrates that touch input 705 remains at location 705-D ontouch screen 112 for a period of time (e.g., one or more frames at thedisplay rate), that corresponds to the delay between receiving a touchinput and displaying a user interface that is updated based on the touchinput. While touch input 705 remains at location 705-D on touch screen112, a user interface prepared based on travel distance 740-6 isdisplayed, in which length 750-7 of line 704-4 matches travel distance740-8 of touch input 705.

As explained above, the delay between receiving a touch input anddisplaying a user interface that is updated based on the touch inputleads to a discrepancy between the physical location of the touch inputand a position of the touch input reflected in the displayed userinterface.

Although FIGS. 7B-7E, the delay between receiving a touch input anddisplaying a user interface that reflects a status (e.g., a location) ofthe touch input corresponds to a single display frame, in someembodiments, the delay corresponds to more than one display frame.

FIGS. 7F-7O are timing diagrams that show timing of receiving touchinputs (or changes to touch inputs) and timing of displaying (orupdating) user interfaces in accordance with some embodiments. In FIGS.7F-7O, upward arrows (e.g., 720 and 722) represent timing of touchinputs (or changes to touch inputs) and downward arrows 730 representtiming of displaying (or updating) user interfaces.

FIG. 7F illustrates that touch inputs are received at different times720-1, 720-2, 720-3, and 720-4 and a user interface is updated at times730-1, 730-2, 730-3, and 730-4. In FIG. 7F, the detection rate and thedisplay rate are the same (e.g., both the detection rate and the displayrate are 60 Hz). In FIG. 7F, the detection rate and the display rate aresynchronized (e.g., there is no phase difference). For example, thetouch input received at 720-1 is concurrent with an update to the userinterface at 730-1. Similarly, the touch input received at 720-2 isconcurrent with an update to the user interface at 730-2.

FIG. 7F also illustrates that the touch input received at 720-1 isreflected after one display frame (e.g., 730-2), after two displayframes (e.g., 730-3), or after three display frames (e.g., 730-4). Insome embodiments, the touch input received is reflected after more thanthree display frames. In some embodiments, the number of display framesbetween receiving a touch input and displaying a user interface thatreflects the received touch input is determined based on delay inprocessing the received touch input and preparing the user interface fordisplay. In some embodiments, the delay between receiving a touch inputand displaying a user interface that is updated based on the touch inputincludes time spent by one or more of: the touch-sensor hardwarescanning to detect the touch, the contact-motion module identifying thetouch and determining the application to which to deliver the touch (ortouch events associated with the touch); the application processing thetouch to determine how to update the display in response to the touch,and generating display update information; an operating system graphicscomponent (e.g., a display driver) rendering a display frame based onthe display update information from the application; a graphicsprocessing unit (GPU) converting the display frame generated by theoperating system graphics component into display update instructions(e.g., a map of pixels to be displayed on the display); and a displayrefresh operation (e.g., the time spent actually updating the pixels ofthe display to reflect the display update instructions and show theupdates to the user interface generated by the application in responseto receiving the touch).

FIG. 7G is similar to FIG. 7F except that the detection rate and thedisplay rate are not synchronized. In FIG. 7G, the detection rate andthe display rate are the same (e.g., both the detection rate and thedisplay rate are 60 Hz). However, there is phase difference betweendetection timing and display timing. For example, timing of receivingtouch inputs is offset from timing of updating the user interface.

FIG. 7G also illustrates that the touch input received at 720-1 isreflected in a next display frame (e.g., 730-2), in a display framesubsequent to the next display frame (e.g., 730-3), or in two displayframes subsequent to the next display frame (e.g., 730-4). In someembodiments, the touch input received is reflected in a display framesubsequent to 730-4.

FIGS. 7F-7G illustrate timing of touch inputs and display updates inconventional devices in accordance with some embodiments. Suchconventional devices suffer from the delays described above with respectto FIGS. 7A-7E.

FIGS. 7H-7O are timing diagrams that show detection rates (e.g., a touchdetection rate that corresponds to a rate at which a touch-sensitivesurface is scanned for changes in touch data that is interpreted astouches and touch events) higher than a display rate (e.g., a displayrefresh rate that corresponds to the frequency with which the pixels onthe display are redrawn) in accordance with some embodiments.

FIG. 7H illustrates that touch inputs 722 are received at a detectionrate that is four times a display rate. In FIG. 7H, touch inputs arereceived four times while a display is updated once (e.g., the detectionrate is 240 Hz and the display rate is 60 Hz).

In some embodiments, touch inputs are received at a rate that is lessthan a touch-sensitive surface (or one or more touch sensors) is capableof receiving touch inputs. For example, FIG. 7I illustrates that, whilethe touch-sensitive surface is capable of receiving touch inputs at adetection rate that is four times a display rate (e.g., thetouch-sensitive surface is capable of receiving (or detecting) touchinputs four times within each display frame), only touch inputs arereceived only twice within each display frame (e.g., touch inputs arereceived at 722-3 and 722-5, and the device forgoes receiving touchinputs at 722-2 and 722-4). In some embodiments, whether to receive moreor fewer touch inputs within each display frame is determined by thedevice based on predefined criteria, such as accuracy requirements,available computing resources, etc. In some embodiments, a number oftouch inputs received within each display frame is adjusted dynamicallyby the device based on the predefined criteria (e.g., receiving moretouches when the discrepancy between the current detected location ofthe touch and the actual location of the touch is likely to be greaterthan a predefined amount, such as when the touch is moving quickly orlarger discrepancies have been detected in recent display frames, andreceiving fewer touches when the discrepancy between the currentdetected location of the touch and the actual location of the touch issmaller than the predefined amount, such as when the touch is movingslowly or smaller discrepancies have been detected in recent displayframes).

FIGS. 7J-7K illustrate touch detection frames, touch processing frames,and touch display frames in accordance with some embodiments.

FIG. 7J illustrates that touch detection frame 724-1 includes touchinputs at 722-2, 722-3, 722-4, and 722-5 and touch detection frame 724-2includes touch inputs at 722-6, 722-7, 722-8, and 722-9.

FIG. 7J also illustrates touch processing frames 732-1, 732-2, 732-3,732-4, and 732-5. In some embodiments, a touch processing framecompletely overlaps with a touch detection frame (e.g., touch processingframe 732-2 completely overlaps with touch detection frame 724-1). Insome embodiments, touch inputs (or corresponding locations) in touchdetection frame 724-1 are processed during touch processing frame 732-2(which overlaps with touch detection frame 724-1), and displayed duringdisplay frame 734-2. In some embodiments, touch inputs (or correspondinglocations) in touch detection frame 724-1 are processed during touchprocessing frame 732-3 (which does not overlap with touch detectionframe 724-1), and displayed during display frame 734-3.

FIG. 7K is illustrates that touch detection frame 724-3 includes touchinputs at 722-1, 722-2, 722-3, and 722-4 and touch detection frame 724-4includes touch inputs at 722-5, 722-6, 722-7, and 722-8. In FIG. 7K, atouch detection frame is not aligned with a display frame (e.g., touchdetection frame 724-4 includes touch 722-5 that is received duringdisplay frame 734-1 and touch 722-6 that is received during displayframe 734-2). In some embodiments, touch inputs in touch detection frame724-3 are processed during touch processing frame 732-2, which partiallyoverlaps with touch detection frame 724-3, and displayed during displayframe 734-2.

FIGS. 7L and 7M illustrate selection of touch inputs based on timingcriteria in accordance with some embodiments.

FIG. 7L illustrates that a group of touch inputs is selected based onfirst predefined timing criteria. For example, group 724-5 of touchinputs is selected so that touch inputs in group 724-5 precedes asubsequent timing of updating a user interface by at least a particulartiming margin (e.g., Δt). In FIG. 7L, a last touch input in group 724-5precedes timing 730-3 for updating a user interface by the particulartiming margin (e.g., Δt). FIG. 7L also illustrates that the same timingmargin is used for each selection. For example, group 724-6 of touchinput is selected touch inputs in group 724-6 also precedes subsequenttiming 730-4 of updating a user interface by at least the sameparticular timing margin (e.g., Δt).

FIG. 7M illustrates use of different timing margins. In FIG. 7M, group724-7 of touch inputs is selected between a first point in time thatprecedes timing 730-2 for updating a user interface by timing margin Δt₁and a second point in time that precedes timing 730-3 for updating theuser interface by timing margin Δt₂. Touch inputs in group 724-8 aresubsequent to touch inputs in a preceding group, namely group 7247-7,and precede timing 730-4 for updating the user interface by timingmargin Δt₃. In some embodiments, different timing margins are used fordefining respective touch processing frames, as shown in FIG. 7M.

FIG. 7N illustrates selection of representative touches in accordancewith some embodiments. In FIG. 7N, set 724-5 of touch inputs includestouch inputs 722-3, 722-4, 722-5, and 722-6, and touch input 722-6 isselected as a representative touch (and a corresponding touch locationis selected as a representative touch location) for set 724-5 of touchinputs. Similarly, set 724-6 of touch inputs includes touch inputs722-7, 722-8, 722-9, and 722-10, and touch input 722-10 is selected as arepresentative touch (and a corresponding touch location is selected asa representative touch location) for set 724-6 of touch inputs. In FIG.7N, a last touch input in the set 724-5 of touch inputs (e.g., touchinput 722-6) is selected as a representative touch for set 724-5 oftouch inputs. Alternatively, a first touch input in set 724-5 of touchinputs (e.g., touch input 722-3) or any other touch input in set 724-5of touch inputs is selected as a representative touch for set 724-5 oftouch inputs. Touch inputs that are located between representativetouches (e.g., touch inputs 722-7, 722-8, and 722-9 betweenrepresentative touches 722-6 and 722-10) are called herein interstitialtouches (and their corresponding locations are called hereininterstitial touch locations).

The selection of representative touches has the effect of shifting thetouch processing frame. For example, selecting touch 722-6 as arepresentative touch for update time 730-3 has the effect of shiftingthe touch processing time by a quarter of a display update frame (e.g.,˜16.667 ms) from selecting touch 722-5 as a representative touch. Byshifting the touch processing time (through selection of touch 722-6 asa representative touch), the discrepancy between the detected touch andthe displayed user interface is reduced (e.g., because more recent touchinformation from the shifted touch processing time is used for updatingthe user interface than touch information without shifting the touchprocessing time). Selecting touch 722-7 as a representative touch forupdate time 730-3 would have the effect of shifting the touch processingtime by half of the display update frame (e.g., ˜33.333 ms) and furtherreduce the discrepancy between the detected touch and the displayed userinterface if there is sufficient processing margin time between touch722-7 and update time 730-3. However, touch 722-7 does not precedeupdate time 730-3 by processing margin time Δt, and thus, touch 722-7 isnot selected as a representative touch for update time 730-3.

FIG. 7O illustrates that set 724-7 of touch inputs includes detectedtouches, such as representative touch 722-6 and interstitial touches722-3, 722-4, and 722-5. In addition, set 724-7 includes one or morepredicted touches. In FIG. 7O, set 724-7 includes predicted interstitialtouches 722-7, 722-8, and 722-9. In some embodiments, set 724-7 includesone or more predicted representative touches (e.g., touch 722-10).

FIG. 7P illustrates use of interstitial touch locations in updating auser interface in accordance with some embodiments. FIG. 7P is similarto FIG. 7D except that interstitial locations 742-1, 742-2, 742-3,742-4, and 742-5 are used to update the user interface. When the traveldistance is at 740-6, travel distance 742-5 is used (instead of traveldistance 740-5 as shown in FIG. 7D) as length 750-5 of line 704-5, anddiscrepancy d₃ between the actual travel distance (e.g., 740-6) and thedisplayed length (e.g., 750-5) of line 704-5 is reduced (e.g., less thandiscrepancy d₂ shown in FIG. 7D).

FIGS. 7Q-7OO illustrate use of predicted touch locations and associatedoperations in accordance with some embodiments.

FIGS. 7Q-7V illustrate that use of predicted touch locationssignificantly reduces, or eliminates, discrepancy between a detectedtouch location and a displayed touch location.

When touch input 707 moves from location 707-A (shown in FIG. 7Q) tolocation 707-B (shown in FIG. 7R), the user interface may not be updatedimmediately to reflect the actual location of touch input 707 (e.g.,707-B) due to various delays. Instead of waiting for the actual locationof touch input 707 to be made available, the device predicts a locationof touch input 707. In FIG. 7R, predicted location 710-1 matches actuallocation 707-B of touch input 707, and any discrepancy between theactual location of touch input 707 and a displayed location of touchinput 707 (e.g., an end point of line 704-6) is reduced or eliminated.

Similarly, FIGS. 7S-7V illustrate that use of the predicted locationsreduces, or eliminates, discrepancy between a detected touch locationand a displayed touch location.

FIGS. 7W-7BB are similar to FIGS. 7Q-7V except that one or more userinterface objects that correspond to one or more predicted touchlocations are visually distinguished (displayed with different color,line width, shape, shading, highlighting, line styles, etc.) from one ormore user interface objects that are independent of one or morepredicted touch locations.

In FIG. 7W, line 706-1 that extends from an initial location of touchinput 707 (e.g., location 707-A in FIG. 7Q) to predicted location 710-1of touch input 707 is depicted as a thin dashed line. In FIG. 7X, afterthe actual location of touch input 707 at location 707-B is received,line 706-1 that represents predicted movement of touch input 707 isreplaced with line 708-1 (e.g., a thick solid line) that is visuallydistinguished from line 706-1. Replacing line 706-1 (in FIG. 7W) withline 708-1 indicates that predicted location 710-1 (in FIG. 7W) matchesactual location 707-B of touch input 707.

FIG. 7X also illustrates that line 706-2 that extends from location707-B to predicted location 710-2 of touch input 707 is displayed with avisual distinction to indicate that line 706-2 is based on a predictedlocation of touch input 707 (e.g., location 710-2).

Similarly, FIG. 7Y-7BB illustrate visual distinctions of user interfaceobjects or portions thereof, to indicate that such user interfaceobjects (or portions) are based on one or more predicted touchlocations.

Although FIGS. 7Q-7BB illustrate embodiments, in which predictedlocations match actual locations of touch inputs, predictions need notbe perfectly accurate. For example, a predicted location positionedbetween the previous location of the touch input and the currentlocation of the touch input (instead of being positioned precisely atthe current location of the touch input) reduces the discrepancy betweenthe current location of the touch input and the displayed userinterface, thereby improving accuracy of the displayed user interface.

FIGS. 7CC-7FF illustrate user interfaces associated with predicted touchlocations in accordance with some embodiments.

In FIG. 7CC, line 706-3 extends to predicted location 710-3 thatcorresponds to touch location 707-D of touch input 707. Subsequently, asshown in FIG. 7DD, line 706-4 extends to predicted location 710-4 andtouch input 707 moves to location 707-G that does not correspond topredicted location 710-4.

FIG. 7EE illustrates that line 706-4 is removed (e.g., because predictedlocation 710-4 does not correspond to actual location 707-G of touchinput 707 and, optionally, the distance between predicted location 710-4and actual location 707-G is more than predefined threshold). Instead,line 708-6 that corresponds to actual location 707-G of touch input 707is displayed.

FIG. 7EE also illustrates that line 706-6 that extends to predictedlocation 710-6 is displayed on touch screen 112. Touch input 707 movesto location 707-H that does not correspond to predicted location 710-6.In some embodiments, in accordance with a determination that thedistance between predicted location 710-6 and actual location 707-H isless than the predefined threshold, line 706-6 is included in line 708-7to indicate that predicted location 710-6 does not deviate from actuallocation 707-H by more than the predefined threshold, as shown in FIG.7FF.

FIGS. 7GG and 7HH are similar to FIGS. 7DD and 7EE except that the userinterfaces in FIGS. 7GG and 7HH do not include user interface objects(or portions thereof) that are visually distinguished to indicate thatthe user interface objects (or portions thereof) correspond to one ormore predicted touch locations.

FIG. 7II illustrates that touch inputs (e.g., movement of a contact ontouch screen 112) are detected at a plurality of locations on touchscreen 112. The locations include detected touch locations (e.g.,detected representative touch locations 712-1, 712-2, and 712-3, anddetected interstitial touch locations 714-1 through 714-6) and predictedtouch locations (e.g., predicted representative touch locations 716-1and 716-2 and predicted interstitial touch locations 718-1 through718-6).

In some embodiments, the device 100 includes one or more sensors todetect intensity applied by a contact on touch screen 112. FIG. 7II alsoillustrates that intensity of the contact is detected at multiplelocations (e.g., 760) and, optionally, predicted intensity is determined(e.g., 762).

In some embodiments, the device 100 includes one or more sensors todetect a tilt and/or an orientation of a stylus associated with thedevice 100. FIG. 7II illustrates that a tilt and/or an orientation ofthe stylus is obtained (e.g., 770) and, optionally, predicted tiltand/or orientation is determined (e.g., 772).

In some embodiments, detecting intensity applied by a contact on touchscreen 112, detecting a tilt of a stylus, and/or detecting anorientation of the stylus take a different amount of time than detectinga location of a touch input. In some embodiments, one or more sensorsused for detecting intensity applied by a contact on touch screen 112,detecting a tilt of a stylus, and/or detecting an orientation of thestylus have a longer latency than one or more sensors used for detectinga location of a touch input. Thus, in some embodiments, predictedintensity, predicted tilt, and/or predicted orientation are used evenfor “known” (e.g., detected and processed) touch locations.

FIG. 7JJ illustrates that a number of predicted locations is determinedat least in part based on a confidence level associated with thepredicted touches. For example, differences between predicted locationsand detected locations (e.g., difference between predicted location718-1 and detected location 714-7 and/or difference between predictedlocation 718-2 and detected location 714-8) are used to determine thenumber of predicted locations. When the difference increases, the numberof predicted locations is reduced (e.g., because the prediction is lessreliable), and when the difference decreases, the number of predictedlocation is increased (e.g., because the prediction is more reliable).

FIG. 7KK illustrates that the number of predicted locations isdetermined at least in part based on a confidence level associated withdetected touches. For example, increased variation in the detectedtouches (e.g., deviations from a reference line as shown in FIG. 7KK)reduces the number of predicted touches, and decreased variation in thedetected touches increases the number of predicted touches.

FIG. 7LL illustrates that the number of predicted locations isdetermined at least in part based on a speed of the touch input. Forexample, when the speed of the touch input decreases, the number ofpredicted touches decreases (e.g., because there can be more jitter at alower speed), and when the speed of the touch input increases, thenumber of predicted touches increases (e.g., because the touch input,such as a finger or stylus, is less likely to suddenly changedirection). Typically, a fast-moving touch input has a smallerdifference or error between the predicted touches and the actual touchesthan a slow-moving touch input. In addition, as explained above withrespect to FIGS. 7B-7E, when coalesced touches or predicted touches arenot used, a fast-moving touch input suffers more from a largediscrepancy between actual touches and displayed user interfaces than aslow-moving touch input. Such large discrepancy can be reduced oreliminated by use of predicted touches, which are typically moreaccurate with fast-moving touch inputs than with slow-moving touchinputs. Therefore, it is especially advantageous to use predictedtouches for fast-moving touch inputs, thereby significantly reducing oreliminating the discrepancy between detected touches and displayed userinterfaces.

Although FIGS. 7II-7LL illustrate predicted locations arranged in astraight line, predicted locations are not limited to straight lines.FIG. 7MM illustrates that detected locations 712-12 and 712-13 and714-19 through 714-22 define a curve, and predicted locations on thecurve (e.g., 718-11 through 718-13 and 716-5) are determined.

FIGS. 7NN-7OO illustrate drawing a line with a touch input in someembodiments. In FIGS. 7NN-7OO, a width of a respective portion of theline is based on intensity applied by the touch input at a location thatcorresponds to the respective portion of the line. For example, moving atouch input at a high intensity initiates drawing a wide line, andmoving a touch input at a low intensity initiates drawing a thin line.

FIG. 7NN illustrates that touch input 709 moves across touch screen 112and a corresponding line is displayed on touch screen 112. Movement oftouch input 709 includes first portion 780 and second portion 782. InFIG. 7NN, touch screen 112 displays portion 784 of the line thatcorresponds to first portion 780 of the movement of touch input 709 andportion 786 of the line that corresponds to a predicted movement oftouch input 709 (e.g., portion 786 is based on predicted location andpredicted intensity). For example, while touch input 709 has followedpath 780 and path 782, movement of touch input 709 along path 780 isdetected and processed so that portion 784 that corresponds to firstportion 780 of the actual movement of touch input 709 is displayed.Movement of touch input 709 along path 782 is not reflected in the userinterface and instead portion 786 of the line that is based on predictedtouch information (e.g., predicted location and intensity) is shown.

FIG. 7OO illustrates that, subsequent to displaying the user interfaceshown in FIG. 7NN, the user interface is updated so that portion 786 ofthe line is replaced with portion 788 of line based on detected movementof touch input 709 (e.g., portion 788 is based on detected movement 782of touch input 709 including the detected location and the detectedintensity of touch input 709). The changes to the width in portion 788of the line indicates actual changes to the intensity of touch input 709while the touch input 709 was following path 782. In some embodiments,portion 786 of the line is replaced with portion 788 of line with asmooth transition (e.g., sub-portions of portion 786 are replacedsequentially with sub-portions of portion 788), instead of suddenlyreplacing portion 786 with portion 788 all at once.

Although FIGS. 7A-7OO illustrate processing finger inputs, a personhaving ordinary skill in the art would understand that the methods andthe user interfaces illustrated in FIGS. 7A-7OO can be applied toprocessing stylus inputs and/or mouse inputs, in an analogous manner.For brevity, such details are not repeated herein.

FIGS. 8A-8B illustrate a flow diagram of method 800 of updating a userinterface based on coalesced touch locations in accordance with someembodiments. Method 800 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display and a touch-sensitive surface. In some embodiments, theelectronic device includes one or more sensors to detect intensity ofcontacts with the touch-sensitive surface. In some embodiments, thedisplay is a touch-screen display and the touch-sensitive surface is onor integrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method 800are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, method 800 provides a way to update a user interfacebased on coalesced touch locations. The method reduces discrepanciesbetween detected touch inputs and displayed user interfaces, therebyreducing the cognitive burden on a user when interacting with a touchscreen. In addition, this creates a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user tointeract with the user interface more accurately reduces errors andunnecessary corrections, thereby conserving power and increasing thetime between battery charges.

The device displays (802) a user interface at a first display rate(e.g., FIG. 7P).

While displaying the user interface, the device detects (804), at afirst detection rate that is greater than the first display rate,movement of a touch input at a sequence of locations on thetouch-sensitive surface. For example, in FIG. 7H, the detection rate isfour times the display (update) rate. In some embodiments, the firstdetection rate is an integer multiple of the first display rate (e.g.,the first display rate is 60 Hz and the first detection rate is 240 Hz,which is four times 60 Hz). The touch input may be monitored at a rate(e.g., 240 Hz or 250 Hz) that is lower than a maximum scan rate (e.g.,500 Hz) of the touch-sensitive surface. For example, in FIG. 7I, insteadof monitoring the touch input at four times the display rate, the touchinput is monitored twice the display rate.

At each of a sequence of update times, the device updates (806) the userinterface from a respective current state to a respective next state inaccordance with a selected subset of the sequence of locations of thetouch input, each selected subset of the sequence of locationscomprising a plurality of locations of the touch input. For example, asshown in FIG. 7J, the user interface is updated at each of a sequence ofupdate times (e.g., at 730-1, 730-2, 730-3, and 730-4). In someembodiments, the respective next state of the user interface is distinctfrom the respective current state of the user interface (e.g., the userinterface changes over time so that the respective next state of theuser interface appears differently from the respective current state ofthe user interface). In some embodiments, the user interface may updatedone or more frames after the frame that immediately follows thedetection of the last location in the first set of sequential locations,depending on the processing time. In some embodiments, the sequence ofupdate times is determined in accordance with the first display rate.For example, for the user interface displayed at 60 Hz, the userinterface is updated approximately every 16.67 ms (≈1/(60 Hz)).

In some embodiments, the device sends (808) to a first softwareapplication a message having information that includes the selectedsubset of the sequence of locations, and the first software applicationupdates the user interface in accordance with the information in themessage. For example, in FIG. 7J, set 724-1 of touch inputs is sent tothe first software application (e.g., a drawing application) at 730-2,and the first software application updates the user interface at 730-3in accordance with the information in set 724-1.

In some embodiments, the message also includes (810) informationidentifying one or more of: intensity of the touch input at the selectedsubset of the sequence of locations (e.g., intensity 252 in FIG. 1D);and a type of the touch input detected at the selected subset of thesequence of locations (e.g., whether the touch input is made with afinger or a stylus, such as touch type 258 in FIG. 1D). In someembodiments, the message also includes information identifying timing ofthe touch input at the selected subset of the sequence of locations(e.g., timestamp 256 in FIG. 1D).

In some embodiments, a last detected location in each selected subset isdetected (812) at least a predefined time interval (e.g., processingmargin time) prior to a next update time (e.g., FIG. 7L). In suchembodiments, the last detected location in each selected subset isprocessed and used for updating the user interface at the next updatetime.

In some embodiments, the device updates (814) the user interface from afirst state to a second state in accordance with a first subset of thesequence of locations of the touch input. In some embodiments, thesecond state of the user interface is distinct from the first state ofthe user interface. Subsequent to updating the user interface from thefirst state to the second state, the device updates the user interfacefrom the second state to a third state in accordance with a secondsubset of the sequence of locations of the touch input. In someembodiments, the third state of the user interface is distinct from thesecond state of the user interface. For example, FIG. 7P illustrates aseries of changes to the user interface (represented by an increasedlength of the displayed line over time in accordance with the touchinput). In some embodiments, the second subset of the sequence oflocations of the touch input is distinct from the first subset of thesequence of locations of the touch input. In some embodiments, thesecond subset of the sequence of locations of the touch input does notoverlap with the first subset of the sequence of locations of the touchinput. For example, the first subset of the sequence of locations of thetouch input and the second subset of the sequence of locations of thetouch input do not include a common location of the touch input. In someembodiments, the first subset of the sequence of locations of the touchinput and the second subset of the sequence of locations of the touchinput include distinct numbers of locations.

In some embodiments, the device selects (816, FIG. 8B) a respectivetouch location in the selected subset of the sequence of locations ofthe touch input as a representative touch location (e.g., representativetouch 722-6 in FIG. 7N).

In some embodiments, the respective touch location is selected (818) asthe representative touch location in accordance with touch-processingcriteria for the first application that indicate an amount of timeneeded by the first application to update the user interface (e.g., asdescribed in greater detail below with reference to FIGS. 9A-9D). Insome embodiments, the amount of time needed by the first application ischecked upon launching the first application. In some embodiments,checking the amount of time needed by the first application is repeated(e.g., at a predefined interval). In some embodiments, the amount oftime needed by the first application changes over time. In someembodiments, a longest amount of time needed by the first applicationfrom the repeated checking of the amount of time needed by the firstapplication is used.

In some embodiments, updating the user interface by the firstapplication includes (820) transmitting the selected subset of thesequence of locations of the touch input to the first application alongwith an indication of which location is the representative touchlocation (e.g., identifiers 214 of representative touches in FIG. 1D).For example, by identifying the representative touch location within themultiple locations, applications that are not expecting to receivemultiple touch locations can simply use the representative touchlocation while applications that know to expect multiple touch locationscan use the representative touch location and the other (interstitial)touch locations to provide a more accurate and responsive userinterface.

In some embodiments, the selected subset of the sequence of locationsincludes (822) one or more interstitial locations that correspond totouch locations between a prior representative touch location and therepresentative touch location (e.g., interstitial touches 722-3, 722-4,and 722-5 in FIG. 7N).

In some embodiments, for each update time in the sequence of updatetimes, the device selects (824) a plurality of locations of the touchinput to use for updating the user interface. The selected locations arelocations of the touch input detected after a last selection oflocations to use for updating the user interface (e.g., in FIG. 7M,touches in set 724-8 are detected after selecting touches in set 724-7).

In some embodiments, the selected plurality of locations of the touchinput includes (826) one or more predicted interstitial locations (e.g.,predicted interstitial touches 722-7, 722-8, and 722-9 in FIG. 7O, andas described in greater detail below with reference to FIGS. 10A-10C).

In some embodiments, for each update time in the sequence of updatetimes, the device selects (828) a plurality of locations of the touchinput to use for updating the user interface. The selected locations arelocations of the touch input detected after detecting locations of thetouch input last selected for updating the user interface (e.g., in FIG.7M, touches in set 724-8 are detected after touches in set 724-7 aredetected). Alternatively, the selected locations are locations of thetouch input, in the sequence of locations, after locations of the touchinput last selected for updating the user interface.

In some embodiments, the selected locations include (830) all of thelocations of the touch input detected after detecting locations of thetouch input last selected for updating the user interface.Alternatively, the selected locations include all of the locations ofthe touch input detected no later than the update time and that compriselocations of the touch input, in the sequence of locations, afterlocations of the touch input last selected for updating the userinterface.

In some embodiments, the selected locations include (832) only one ofthe locations of the touch input detected after detecting locations ofthe touch input last selected for updating the user interface (e.g.,only a single representative touch location is used). In someembodiments, the selected locations include two or more sequentiallocations. In some embodiments, only one location is a most recentlydetected location. In some embodiments, the selected locations include amost recently detected location and an immediately previous location.

In some embodiments, locations of the touch input that have not beenselected are discarded. In some embodiments, locations of the touchinput that have not been selected are included in a subsequent selectedsubset.

It should be understood that the particular order in which theoperations in FIGS. 8A-8B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 900, 1000, and 1100 are also applicable in an analogous mannerto method 800 described above with respect to FIGS. 8A-8B. For example,the touch information, predicted touch locations, representative touchlocations, interstitial touch locations, and information sendingoperations described above with reference to method 800 optionally haveone or more of the characteristics of the touch information, predictedtouch locations, representative touch locations, interstitial touchlocations, and information sending operations described herein withreference to other methods described herein (e.g., methods 900, 1000,and 1100). For brevity, these details are not repeated here.

FIGS. 9A-9D illustrate a flow diagram of method 900 of processing atouch input with a touch processing module in accordance with someembodiments. Method 900 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display and a touch-sensitive surface. In some embodiments, theelectronic device includes one or more sensors to detect intensity ofcontacts with the touch-sensitive surface. In some embodiments, thedisplay is a touch-screen display and the touch-sensitive surface is onor integrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method 900are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, method 900 provides a way to process a touch inputusing a touch processing module. The method provides anapplication-independent touch processing module configured to process atouch input and send processed touch information to an application.Thus, the application does not need its own instructions to process rawtouch inputs, and software applications that utilize representativetouch locations can be developed faster and more efficiently.

The device displays (902) a user interface of a first softwareapplication (e.g., the user interface of a drawing application as shownin FIG. 7P) that is updated at a first display rate (e.g., adisplay-update rate). While displaying a first frame of the userinterface in accordance with the first display rate, the device detects(904) respective movement of a touch input across the touch-sensitivesurface (e.g., detect movement of the contact at a first set of multiplesequential locations on the touch-sensitive surface as the touch movesacross the touch-sensitive surface).

The device, at an application-independent touch processing module (e.g.,using the application-independent touch processing module, such as touchprocessing module 220 in FIG. 1C), performs the following operations(e.g., operations 906-912, 916-920, and 922-934). In some embodiments,the touch processing module is distinct from a portion of the firstsoftware application that is unique to the first software application(e.g., application core 1 (230-1) in FIG. 1C). For example, the touchprocessing module is part of an application development framework thatis provided to the application developer either as a drop-in module thatis integrated with the first application and enables the firstapplication to interact with touch input information provided by theoperating system on which the first application is running, or the touchprocessing module is part of the operating system that provides touchinput information to the first application according to an applicationprogramming interface (API) that specifies a consistent format for thetouch input information. In some embodiments, multiple differentthird-party applications running on the device include independentinstances of the touch processing module. In some embodiments, multipledifferent applications on the device include code for interfacing with atouch processing module that communicates with all of the third-partyapplications. In some embodiments, the touch processing module isseparate from the first software application.

The device selects (906) a respective touch location of the touch inputthat was detected during the respective movement to identify as arepresentative touch location for the respective movement based ontouch-processing criteria for the first software application (e.g.,touch 722-6 is selected as a representative touch in FIG. 7N). In someembodiments, the touch-processing criteria for the first softwareapplication corresponds to processing capabilities of the first softwareapplication (e.g., selecting one or more locations of the first set ofmultiple sequential locations to send to the first software applicationbased on how quickly the first software application can process thetouch input and generate an updated user interface for display on thedisplay).

In some embodiments, selecting the respective touch location as therepresentative touch location includes (916, FIG. 9B) detecting a firsttouch location of the touch input during the touch-detection frame, andin response to detecting the first location: in accordance with adetermination that the first touch location meets the touch-processingcriteria (e.g., a criterion that a next touch location for the touchinput will be detected less than a minimum amount of time before thefirst application needs to process the touch input to generate anupdated user interface based on movement of the contact in time fordisplay during the respective display frame) for the first application,selecting the first touch location as the representative touch locationfor the respective movement of the touch input (and, optionally, sendingthe first touch location to the first application); and, in accordancewith a determination that the first touch location does not meet thetouch-processing criteria for the first application, forgoing selectingthe first touch location as the representative touch location for therespective movement of the touch input (e.g., forgoing sending the firsttouch location to the first application, or waiting to send the firsttouch location to the first application). For example, in FIG. 7N, touch722-7 is not selected for update at 730-3, because the amount of timebetween touch 722-7 and update time 730-3 is less than the minimumamount of time Δt.

In some embodiments, selecting the respective touch location as therepresentative touch location includes (918) detecting a second touchlocation of the touch input during the touch-detection frame, and, inresponse to detecting the second location, in accordance with adetermination that the second touch location meets the touch-processingcriteria (e.g., a criterion that a next touch location for the touchinput will be detected less than a minimum amount of time before thefirst application needs to process the touch input to generate anupdated user interface based on movement of the contact in time fordisplay during the respective display frame) for the first application,selecting the second touch location as the representative touch locationfor the respective movement of the touch input (and, optionally, sendingthe second touch location to the first application). For example, inFIG. 7N, touch 722-6 is selected for update at 730-3, because the amountof time between touch 722-6 and update time 730-3 is more than theminimum amount of time Δt.

In some embodiments, the method includes (920), in accordance with adetermination that the second touch location does not meettouch-processing criteria for the first application, forgoing selectingthe second touch location as the representative touch location for therespective movement of the touch input (e.g., forgoing sending the firsttouch location to the first application, or waiting to send the firsttouch location to the first application). In some embodiments, thedevice detects 3, 4, or more touch locations during the touch-detectionframe and determines whether or not to identify any of the touchlocations as the representative touch location based on thetouch-processing criteria for the first application. In someembodiments, different applications have different touch-processingcriteria (e.g., some applications generate updated user interfaces morequickly and thus can receive later touches and still generate updateduser interfaces in time, while other applications generate updated userinterfaces more slowly and thus need to receive earlier touches togenerated updated user interfaces in time). In some embodiments, thesame application can have different touch-processing criteria atdifferent times (e.g., depending on an amount of CPU or GPU processingbandwidth available to the first application, a complexity of the userinterface of the first application, and/or the resources allocated bythe first application to other tasks).

The device sends (908, FIG. 9A) to an application-specific portion ofthe first software application, which is distinct from the touchprocessing module (e.g., the portion of the first software applicationthat is distinct from the touch processing module does not include thetouch processing module), touch location information for the touch inputthat identifies the respective touch location as the representativetouch location for the respective movement. For example, in FIG. 1C,touch location information is sent from touch processing module 220 toapplication core 1 (230-1).

In some embodiments, the device, at the application-independent touchprocessing module (e.g., using the application-independent touchprocessing module), determines (910) a timing of sending the one or moreselected locations to the first software application; and sends the oneor more selected locations to the first software application inaccordance with the determined timing (e.g., the timing requirementchanges over time as shown in FIG. 7M, and the device determines atiming of sending the one or more selected locations based on thechanged timing requirement).

In some embodiments, the device (e.g., using the application-independenttouch processing module) monitors (912) status of the first softwareapplication (e.g., by monitoring a runloop). The timing is determined inaccordance with the status of the first software application (e.g., sendearly if the first software application is busy (because the firstsoftware application cannot respond fast), send late if the firstsoftware application is not busy (because the first software applicationcan respond fast)).

In some embodiments, the device determines (922, FIG. 9C) a processingmargin time. In some embodiments, the device selects a defaultprocessing margin time that is used for all applications executed by thedevice. In some embodiments, a respective application is associated witha respective processing margin time (e.g., a computationally intensiveapplication has a long processing margin time and a computationallylight application has a short processing margin time). At each of asequence of communication times, each of which precedes a display updatetime in a sequence of display update times by at least the determinedprocessing margin time, the device sends, from the touch processingmodule to the first software application, a set of locations thatincludes one or more selected locations of the touch input during apreceding time period; and, at the first software application (e.g.,using the first software application), updates the first user interfacein time for display at the sequence of display update times inaccordance with the set of locations sent by the touch processing moduleat the sequence of communication times. For example, set 724-5 oftouches (FIG. 7L) that precede update time 730-3 by the processingmargin time is used for updating the user interface at update time730-3, and set 724-6 of touches that precede update time 730-4 by theprocessing margin time is used for updating the user interface at updatetime 730-4.

In some embodiments, determining the processing margin time includes(924) setting the processing margin time to an initial value and thendetermining an updated processing margin time in accordance with one ormore measurements of performance of the first software application(e.g., the processing margin time changes over time as shown in FIG.7M). In some embodiments, the initial value is determined by determiningthe performance of the first software application upon initiating thefirst software application. In some embodiments, the updated processingmargin time is determined at a predefined time interval. In someembodiments, the updated processing margin time is in response todetecting each separate touch input on the touch-sensitive surface.

In some embodiments, the processing margin time is determined (926) inaccordance with a longest processing time by the first softwareapplication while processing each of a plurality of sets of touch inputlocations (e.g., if the processing time oscillates or varies, pick aworst case or conservative margin time). In some embodiments, theprocessing margin time is selected from a plurality of candidate margintimes in accordance with confidence values associated with respectivecandidate margin times.

In some embodiments, the locations of the touch input included in theset of locations sent at each communication time correspond (928) to aplurality of detected locations of the touch input between successivecommunication times in the sequence of communication times (e.g., FIG.7L).

In some embodiments, the device sends (930) to the first softwareapplication predicted touch location information for the touch inputthat identifies one or more predicted touch locations for the respectivemovement (e.g., predicted touches 244 in FIG. 1D). In some embodiments,the predicted touch location information is sent concurrently with thetouch location information (e.g., event object 194 in FIG. 1D includesboth predicted touch location information and detected touch locationinformation). In some embodiments, an application independent sub-moduleof the first software application (e.g., touch processing module 220 inFIG. 1C) identifies one or more predicted touch locations for therespective movement in accordance with a predefined prediction model.

In some embodiments, the device sends (932) the touch locationinformation for the touch input to a plurality of software applications,including the first software application. For example, in FIG. 1C, touchlocation information is sent to both application 1 (136-1) andapplication 2 (136-2).

In some embodiments, the device sends (934) to the first softwareapplication the touch location information for the touch input inaccordance with a determination that the first software application isconfigured to receive the touch location information; and sends to asecond software application that is distinct from the first softwareapplication subsequent touch location information for the touch input inaccordance with a determination that the second software application isconfigured to receive the subsequent touch location information. Forexample, in FIG. 1C, touch location information is sent to bothapplication 1 (136-1) and application 2 (136-2). In someimplementations, when the displayed user interface concurrently includesa user interface of application 1 (136-1) and a user interface ofapplication 2 (136-2), touch location information for touches thatcorrespond to the user interface of application 1 (136-1) is sent toapplication 1 (136-1) and touch location information for touches thatcorrespond to the user interface of application 2 (136-2) is sent toapplication 2 (136-2).

The device, at the first software application (e.g., using the firstsoftware application), updates (914, FIG. 9A) the user interface inaccordance with the touch location information (e.g., the one or morelocations selected by the touch processing module). For example, inFIGS. 7Q-7V, the user interface is updated in accordance with changes tothe touch input (and the corresponding touch information). In someembodiments, the touch processing module (e.g., touch processing module220 in FIG. 1C) sends to the portion of the first software applicationthat is unique to the first software application (e.g., application core1 (230-1) in FIG. 1C) the location information for a priorrepresentative touch prior to the next representative touch is detected,in order to give the first software application time to process theprior representative touch.

In some embodiments, the device sends (936, FIG. 9D) the touch locationinformation with a first portion of the first software application,comprising an application-independent sub-module (e.g., theapplication-independent touch processing module, such as touchprocessing module 220 in FIG. 1C), and updates the user interface with asecond portion of the software application that comprises anapplication-specific sub-module (e.g., application core 1 (230-1) inFIG. 1C). In some embodiments, the touch processing module is anapplication-independent module in communication with theapplication-independent sub-module. In some embodiments, a secondapplication executed by the electronic device also includes theapplication-independent sub-module and, when executed, receives touchlocation information from the touch processing module using theapplication-independent sub-module and updates a respective userinterface of the second application with a second portion of the secondsoftware application that comprises an application-specific sub-moduledistinct from the application-specific sub-module of the first softwareapplication.

In some embodiments, the movement of the touch input is detected (938)during a respective touch-detection frame (e.g., touch-detection frame724-1 in FIG. 7J). An updated user interface of the first application,based on the movement of the touch input, is generated during arespective touch-processing frame (e.g., touch-processing frame 732-2 inFIG. 7J). In some embodiments, the respective touch-detection framepartially overlaps the respective touch-processing frame. In someembodiments, the respective touch-detection frame is concurrent with therespective touch-processing frame. The updated user interface isdisplayed on the display for the duration of a respective display frame(e.g., display frame 734-2 in FIG. 7J) that occurs after the respectivetouch-processing frame.

In some embodiments, during the respective touch-processing frame (e.g.,for the entire duration of the respective touch-processing frame), thedevice displays (940) a user interface for the first application thatwas generated during a prior touch-processing frame (e.g., during aprior display frame that occurs concurrently with the respectivetouch-processing frame). For example, in FIG. 7J, duringtouch-processing frame 732-3, a user interface that was generated duringtouch-processing frame 732-2 is displayed.

In some embodiments, during the respective display frame (e.g., for theentire duration of the respective display frame), the device detects(942) subsequent movement of the touch input across the touch-sensitivesurface and sends to (the application-specific portion of) the firstsoftware application touch location information for the subsequentmovement of the touch input (e.g., during a subsequent touch-detectionframe that occurs concurrently with the respective display frame). Forexample, during display frame 734-2, the device detects touches in touchdetection frame 724-2.

It should be understood that the particular order in which theoperations in FIGS. 9A-9D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 1000, and 1100) are also applicable in an analogous mannerto method 900 described above with respect to FIGS. 9A-9D. For example,the touch information, representative touch locations, timing, andinformation sending operations described above with reference to method900 optionally have one or more of the characteristics of the touchinformation, representative touch locations, timing, and informationsending operations described herein with reference to other methodsdescribed herein (e.g., methods 800, 1000, and 1100). For brevity, thesedetails are not repeated here.

FIGS. 10A-10C illustrate a flow diagram of method 1000 of updating auser interface based on predicted touch locations in accordance withsome embodiments. Method 1000 is performed at an electronic device(e.g., device 300, FIG. 3, or portable multifunction device 100, FIG.1A) with a display and a touch-sensitive surface. In some embodiments,the electronic device includes one or more sensors to detect intensityof contacts with the touch-sensitive surface. In some embodiments, thedisplay is a touch-screen display and the touch-sensitive surface is onor integrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method1000 are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, method 1000 provides a way to update a userinterface based on predicted touch locations. The method reducesdiscrepancies between detected touch inputs and displayed userinterfaces, thereby reducing the cognitive burden on a user wheninteracting with a touch screen. In addition, this creates a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to interact with the user interface moreaccurately reduces errors and unnecessary corrections, therebyconserving power and increasing the time between battery charges.

The device displays (1002) a user interface at a first display rate(e.g., the user interface of a drawing application in FIG. 7Q).

While displaying the user interface in accordance with the first displayrate, the device detects (1004) movement of a touch input, includingdetecting the touch input at a first set of sequential locations on thetouch-sensitive surface. The first set of sequential locations includesa plurality of locations on the touch-sensitive surface. For example, inFIG. 7H, a plurality of touches (e.g., touches 722-2 through 722-5) isdetected between display update times 730-1 and 730-2.

In some embodiments, the movement of the touch input is detected (1006)at a first detection rate that is higher than the first display rate(e.g., in FIG. 7H, the detection rate is four times the display rate).

The device predicts (1008) for the touch input a first set of one ormore predicted locations on the touch-sensitive surface based onmultiple locations in the first set of sequential locations. Forexample, in FIG. 7O, touches 722-3 through 722-6 are used to predicttouch locations 722-7 through 722-13. In some embodiments, the first setof one or more predicted locations is predicted based on derivatives(e.g., first derivatives and/or second derivatives) of the multiplelocations in the first set of sequential locations. In some embodiments,the first set of one or more predicted locations is predicted based on alinear fit (e.g., as illustrated in FIG. 7I(K).

In some embodiments, each of the one or more predicted locations is(1010) a predicted representative touch location (e.g., predictedrepresentative touch location 722-10 in FIG. 7O).

In some embodiments, the one or more predicted locations include (1012)one or more predicted interstitial touch locations of the touch input onthe touch-sensitive surface (e.g., predicted interstitial touchlocations 722-7 through 722-9 in FIG. 7O).

In some embodiments, the one or more predicted locations of the touchinput on the touch-sensitive surface are predicted (1014, FIG. 10B)based at least in part on multiple representative touch locations of thetouch input on the touch-sensitive surface (see discussion of therepresentative touch locations above with respect to FIGS. 8A-8B). Forexample, the predicted locations are based on representative touchlocations 722-2 and 722-6 in FIG. 7O. In some embodiments, each displayframe has a single representative touch location.

In some embodiments, the one or more predicted locations of the touchinput on the touch-sensitive surface are predicted (1016) based onmultiple representative touch locations of the touch input on thetouch-sensitive surface and one or more interstitial locations of thetouch input on the touch-sensitive surface (see discussion of theinterstitial touch locations above with respect to FIGS. 8A-8B). Forexample, the predicted locations are based on representative touchlocations 722-2 and 722-6 and interstitial touch locations 722-3 through722-5 in FIG. 7O. In some embodiments, each display frame has one ormore interstitial touch locations that are distinct from therepresentative touch location.

In some embodiments, a number of predicted locations in the first set ofone or more predicted locations of the touch input is determined (1018)in accordance with one or more confidence values associated with the oneor more predicted locations. For example, as shown in FIG. 7JJ, theconfidence values are determined based on whether the predicted touchlocations subsequently match the detected (actual) touch locations.Thus, when the predicted touch locations match the detected touchlocations, the confidence values increase (and, in turn, the number ofpredicted locations increases). When the predicted touch locations donot match the detected touch locations (or the predicted touch locationsdeviate from the detected touch locations by more than predefined errormargin), the confidence values decrease (and, in turn, the number ofpredicted locations decreases). In some embodiments, the touchprocessing module (e.g., touch processing module 220 in FIG. 1C)predicts touch locations. In some embodiments, the touch processingmodule determines a confidence value associated with each touchlocation. In some embodiments, only touch locations that have associatedconfidence values that satisfy confidence value criteria (e.g., areabove a predefined confidence value threshold) are included in the firstset of one or more predicted locations.

In some embodiments, a number of predicted locations in the first set ofone or more predicted locations of the touch input is determined (1020)in accordance with one or more confidence values associated with themultiple locations in the first set of sequential locations. Forexample, as shown in FIG. 7KK, the confidence values are determinedbased on whether the detected touch locations match a prediction model.For example, when the prediction is based on a line fit, the devicedetermines whether the detected touch locations fit onto a fit line.Deviations of the detected touch locations from the line decrease theconfidence values (and, in turn, the number of predicted locationsdecreases). When the detected touch locations fit well to the line, theconfidence values increase (and, in turn, the number of predictedlocations increases). In some embodiments, the touch processing moduledetermines a confidence value for the multiple locations in the firstset of sequential locations. The number of predicted locations isdetermined based on the confidence value for the multiple locations inthe first set of sequential locations (e.g., more predicted locationsfor a high confidence value and fewer predicted locations for a lowerconfidence value).

In some embodiments, the number of predicted locations in the first setof one or more predicted locations of the touch input equals a number oflocations in the first set of sequential locations. In some embodiments,the number of predicted locations in the first set of one or morepredicted locations of the touch input is more than a number oflocations in the first set of sequential locations. In some embodiments,the number of predicted locations in the first set of one or morepredicted locations of the touch input is an integer multiple oflocations in the first set of sequential locations.

In some embodiments, the one or more confidence values associated withthe multiple locations in the first set of sequential locations arebased (1022) at least in part on errors in fitting the multiplelocations in the first set of sequential locations to a predefinedconstraint (e.g., errors in fitting detected touch locations to areference line as shown in FIG. 7KK). In some embodiments, thepredefined constraint is a linear fit to the multiple locations in thefirst set of sequential locations. In some embodiments, the predefinedconstraint is a polynomial fit to the multiple locations in the firstset of sequential locations. In some embodiments, the predefinedconstraint is a circular fit to the multiple locations in the first setof sequential locations. In some embodiments, the one or more confidencevalues associated with the first set of sequential locations are basedat least in part on historical errors (e.g., errors in fitting priorsets of sequential locations). In some embodiments, the one or moreconfidence values associated with the multiple locations in the firstset of sequential locations are based at least in part on historicalconfidence values (e.g., confidence values for prior sets of sequentiallocations). In some embodiments, the one or more confidence valuesassociated with the multiple locations in the first set of sequentiallocations are based at least in part on an orientation of the touchinput.

In some embodiments, the one or more confidence values associated withthe multiple locations in the first set of sequential locations arebased (1024) at least in part on speed of the movement of the touchinput. For example, a touch input with a high speed has a higherconfidence value (because the touch input is less likely to suddenlychange in direction), and a touch input with a low speed has a lowerconfidence value. For example, in FIG. 7LL, the speed of touch input islow and the confidence values are also low. As a result, the number ofpredicted locations is reduced to two.

In some embodiments, the device includes (1026) one or more sensors todetect intensity of touch inputs on the touch-sensitive surface. Thedevice predicts intensity of the touch input at a plurality of locationson the touch-sensitive surface. For example, FIG. 7II illustrates thatintensity of the touch input is predicted at multiple locations. FIG.7NN illustrates a line drawn based on predicted intensity of the touchinput. In some embodiments, the plurality of locations on thetouch-sensitive surface corresponds to a subset of the first set of oneor more predicted locations on the touch-sensitive surface. In someembodiments, the plurality of locations on the touch-sensitive surfacecorresponds to the first set of one or more predicted locations on thetouch-sensitive surface. The device updates the user interface inaccordance with the predicted intensity of the touch input. In someembodiments, the intensity prediction occurs at a different rate thanthe location prediction (e.g., because intensity prediction includesadditional inputs from intensity sensors on a stylus or measurements ofcontact size that take additional processing time), and the locationestimate for one or more touch inputs are updated before the intensityestimates for those touch inputs are updated. As such, the predictedlocation of a touch can be updated in one frame, while the predictedintensity of the touch is updated in a subsequent frame. Additionally,in some embodiments, the predicted intensity of a touch is updated inmultiple subsequent frames, as predicted values for the intensity of thetouch become increasingly accurate.

In some embodiments, the device predicts (1028) tilt and/or orientationof the touch input at a plurality of locations on the touch-sensitivesurface. For example, FIG. 7II illustrates that tilt and/or orientationof the touch input (e.g., a stylus) are predicted at multiple locations.In some embodiments, the plurality of locations on the touch-sensitivesurface corresponds to a subset of the first set of one or morepredicted locations on the touch-sensitive surface. In some embodiments,the plurality of locations on the touch-sensitive surface corresponds tothe first set of one or more predicted locations on the touch-sensitivesurface. The device updates the user interface in accordance with thepredicted tilt and/or orientation of the touch input. In someembodiments, the tilt and/or orientation prediction occurs at adifferent rate than the location prediction (e.g., because tilt and/ororientation prediction includes additional inputs from force sensors ona stylus or measurements of contact shape that take additionalprocessing time), and the location estimate for one or more touch inputsare updated before the tilt and/or orientation estimates for those touchinputs are updated. Additionally, in some embodiments, the predictedtilt and/or orientation of a touch is updated in multiple subsequentframes, as predicted values for the tilt and/or orientation of the touchbecome increasingly accurate.

The device updates (1030, FIG. 10C) the user interface in accordancewith the first set of one or more predicted locations of the touch inputon the touch-sensitive surface. For example, as shown in FIGS. 7Q-7V,the user interface is updated to display an extension of a line based onpredicted touch locations.

In some embodiments, the movement of the touch input is detected (1032)during a respective touch-detection frame (e.g., touch-detection frame724-1 in FIG. 7J). An updated user interface, based on the movement ofthe touch input, is generated during a respective touch-processing frame(e.g., touch-processing frame 732-2). In some embodiments, therespective touch-detection frame partially overlaps the respectivetouch-processing frame (e.g., touch-processing frame 732 overlapstouch-detection frame 724-1). In some embodiments, the respectivetouch-detection frame is concurrent with the respective touch-processingframe (e.g., touch-detection frame 724-1 is concurrent withtouch-processing frame 732). The updated user interface is displayed onthe display for the duration of a respective display frame (e.g.,display frame 734-2) that occurs after the respective touch-processingframe.

In some embodiments, the multiple locations need not be detected duringthe same display frame. Updating the user interface can be at the nextfame time after a representative location of the touch input in thefirst set is detected, or it can be at a later time frame, depending onthe required processing time (e.g., a user interface updated based ontouches detected during touch-processing frame 732-2 is displayed duringdisplay frame 734-3 or 734-4).

In some embodiments, the device, at an application-independent touchprocessing module (e.g., using the application-independent touchprocessing module), predicts (1034) for the touch input the first set ofone or more predicted locations on the touch-sensitive surface; andsends to an application-specific portion of the first softwareapplication the first set of one or more predicted locations of thetouch input on the touch-sensitive surface. For example, in FIG. 1C,predicted touch locations are sent from touch processing module 220 toapplication core 1 (230-1). In some embodiments, the first set of one ormore predicted locations of the touch input on the touch-sensitivesurface is sent to multiple software applications. In some embodiments,the first set of one or more predicted locations of the touch input onthe touch-sensitive surface is posted, and the posted first set of oneor more predicted locations of the touch input is retrieved by one ormore software applications. In some embodiments, the first set of one ormore predicted locations of the touch input on the touch-sensitivesurface is sent from the touch processing module to the first softwareapplication in response to a request from the first software applicationfor the first set of one or more predicted locations of the touch inputon the touch-sensitive surface. The device, at the first softwareapplication (e.g., using the first software application), updates theuser interface in accordance with the first set of one or more predictedlocations of the touch input on the touch-sensitive surface.

In some embodiments, the device, subsequent to detecting the touch inputat the first set of sequential locations on the touch-sensitive surface,detects (1036) the touch input at a second set of sequential locationson the touch-sensitive surface; and compares the second set ofsequential locations of the touch input on the touch-sensitive surfacewith the first set of one or more predicted locations of the touch inputon the touch-sensitive surface. For example, as shown in FIGS. 7CC-7EE,if the difference between the first set of one or more predictedlocations and the detected locations exceeds predefined criteria, theuser interface is updated to remove a user interface object displayedbased on the erroneous prediction. In some embodiments, each touchlocation in the first set of one or more predicted locations of thetouch input on the touch-sensitive surface corresponds to a respectivetouch location in the second set of sequential locations of the touchinput on the touch-sensitive surface. In some embodiments, each touchlocation in the first set of one or more predicted locations of thetouch input on the touch-sensitive surface is associated with arespective timestamp, and is compared with a corresponding touchlocation, in the second set of sequential locations of the touch inputon the touch-sensitive surface, that is associated with the respectivetimestamp. For example, predicted locations correspond to particulartime, such as display update time, which provides illusion of immediateprocessing of touch inputs. In some embodiments, each touch location inthe first set of one or more predicted locations of the touch input onthe touch-sensitive surface is associated with a respective identifier,and is compared with a corresponding touch location, in the second setof sequential locations of the touch input on the touch-sensitivesurface, that is associated with the respective identifier. In someembodiments, the second set of sequential locations of the touch inputon the touch-sensitive surface is compared with the first set of one ormore predicted locations of the touch input on the touch-sensitivesurface by the first software application. In accordance with adetermination that a difference between the first set of one or morepredicted locations of the touch input on the touch-sensitive surfaceand the second set of sequential locations of the touch input on thetouch-sensitive surface satisfies predefined criteria, the deviceupdates the user interface in accordance with the second set ofsequential locations of the touch input on the touch-sensitive surface.

In some embodiments, the device predicts (1038) for the touch input asecond set of one or more locations on the touch-sensitive surface(e.g., based on multiple locations in the second set of sequentiallocations and/or the first set of sequential locations), and updates theuser interface in accordance with the second set of sequential locationson the touch-sensitive surface and the second set of one or morepredicted locations of the touch input on the touch-sensitive surface.For example, in FIGS. 7Z-7AA, both detected touch locations andpredicted touch locations are used for updating the user interface.

In some embodiments, a portion of the user interface that is updated(1040) in accordance with one or more predicted locations is visuallydistinguished from a portion of the user interface that is updated inaccordance with one or more detected locations (e.g., a path based onthe predicted locations is drawn with a dashed line and a path based onthe measured locations is drawn with a continuous line as illustrated inFIGS. 7W-7BB).

It should be understood that the particular order in which theoperations in FIGS. 10A-10C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 900, and 1100) are also applicable in an analogous mannerto method 1000 described above with respect to FIGS. 10A-10C. Forexample, the application programming interface, predicted touchlocations, representative touch locations, and interstitial touchlocations described above with reference to method 1000 optionally haveone or more of the characteristics of the application programminginterface, predicted touch locations, representative touch locations,and interstitial touch locations described herein with reference toother methods described herein (e.g., methods 800, 900, and 1100). Forbrevity, these details are not repeated here.

FIG. 11 illustrates a flow diagram of method 1100 of transferringpredicted touch information in accordance with some embodiments. Method1100 is performed at an electronic device (e.g., device 300, FIG. 3, orportable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the electronic deviceincludes one or more sensors to detect intensity of contacts with thetouch-sensitive surface. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 1100 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 1100 provides a way to transfer predictedtouch information. Use of predicted touch information reducesdiscrepancies between detected touch inputs and displayed userinterfaces, thereby reducing the cognitive burden on a user wheninteracting with a touch screen. In addition, this creates a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to interact with the user interface moreaccurately reduces errors and unnecessary corrections, therebyconserving power and increasing the time between battery charges.

The device displays (1102) a user interface of a first softwareapplication that is updated at a first display rate (e.g., the userinterface of a drawing application in FIG. 7Q).

The device detects (1104) respective movement of a touch input acrossthe touch-sensitive surface at a first detection rate that is higherthan the first display rate (e.g., in FIG. 7H, the detection rate ishigher than the display rate).

The device, at an application-independent touch processing module (e.g.,using the application-independent touch processing module, such as touchprocessing module 220 in FIG. 1C), sends (1106) to anapplication-specific portion of the first software application touchlocation information for the touch input that identifies: one or morepredicted locations of the touch input on the touch-sensitive surface(e.g., location 250 in predicted touches 244, FIG. 1D); and one or morepredicted intensity values of the touch input at one or more intensitylocations of the touch input on the touch-sensitive surface (e.g.,intensity 252 in predicted touches 244, FIG. 1D), the one or moreintensity locations comprising at least a subset of the one or morepredicted locations. In some embodiments, location 250 of predictedtouches 244 in FIG. 1D includes one or more predicted locations of thetouch input and/or one or more predicted intensity locations (e.g., oneor more locations for which intensity is predicted). In someembodiments, a respective intensity value corresponds to a force orpressure applied by the touch input on the touch-sensitive surface. Insome embodiments, the one or more intensity locations are the one ormore predicted locations on the touch-sensitive surface. In someembodiments, the one or more intensity locations are distinct from theone or more predicted locations on the touch-sensitive surface.

The device, at the first software application (e.g., using the firstsoftware application), processes (1122) the touch location information(e.g., application 1 (136-1) in FIG. 1C is used to process the touchlocation information). In some embodiments, processing the touchlocation information includes updating a user interface in accordancewith the touch location information.

In some embodiments, the touch location information includes (1108) arespective touch identifier (e.g., a number or a string that identifiesthe touch associated with each predicted location) for each predictedlocation in the one or more predicted locations of the touch input onthe touch-sensitive surface (e.g., touch identifiers 246 in predictedtouches 244 in FIG. 1D).

In some embodiments, the touch location information also identifies(1110): a plurality of detected locations of the touch input on thetouch-sensitive surface (e.g., location 250 in detected touches 242 inFIG. 1D); and a plurality of intensity values of the touch input at aplurality of intensity locations on the touch-sensitive surface (e.g.,intensity 252 in detected touches 242 in FIG. 1D).

In some embodiments, the plurality of intensity locations on thetouch-sensitive surface is (1112) the plurality of detected locations(e.g., intensity is detected by one or more intensity sensors at samelocations that correspond to locations detected by a touch-sensitivesurface). In some embodiments, the plurality of intensity locations isdistinct from the plurality of detected locations. In some embodiments,the plurality of intensity locations is a subset of the plurality ofdetected locations. In some embodiments, the plurality of detectedlocations is a subset of the plurality of intensity locations.

In some embodiments, the touch location information includes (1114) oneor more touch identifiers for the plurality of detected locations (e.g.,touch identifiers 246 in detected touches 242 in FIG. 1D). In someembodiments, the one or more identifiers for the plurality of detectedlocations do not include the respective identifier for the one or morepredicted locations in the touch location information.

In some embodiments, the touch location information also identifies(1116) predicted tilt and/or orientation of the touch input (e.g.,tilt/orientation 254 in predicted touches 244 in FIG. 1D).

In some embodiments, the touch location information also identifies(1118) a type of the touch input (e.g., whether the touch input is madewith a finger or a stylus as indicated by touch type 258 in FIG. 1D).

In some embodiments, sending to the application-specific portion of thefirst software application touch location information for the touchinput includes (1120) posting the touch location information for thetouch input. For example, event object 194 as illustrated in FIG. 1D isposted in queue 218-1 in FIG. 1C.

It should be understood that the particular order in which theoperations in FIG. 11 has been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 800, 900, and 1000) are also applicable in an analogous mannerto method 1100 described above with respect to FIG. 11. For example, thetouch information, the predicted touch locations, predicted intensity,information sending operations described above with reference to method1100 optionally have one or more of the characteristics of the touchinformation, the predicted touch locations, predicted intensity,information sending operations described herein with reference to othermethods described herein (e.g., methods 800, 900, and 1000). Forbrevity, these details are not repeated here.

In accordance with some embodiments, FIG. 12 shows a functional blockdiagram of an electronic device 1200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 12 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 12, the electronic device 1200 includes a display unit1202 configured to display a user interface, a touch-sensitive surfaceunit 1204 configured to receive contacts, and a processing unit 1208coupled with the display unit 1202 and the touch-sensitive surface unit1204. In some embodiments, the electronic device includes one or moresensor units 1206 configured to detect inputs, and the processing unit1208 is also coupled with the one or more sensor units 1206. In someembodiments, the one or more sensor units 1206 include one or moresensors configured to detect intensity of contacts with thetouch-sensitive surface unit 1204. In some embodiments, the one or moresensor units 1206 include one or more sensors configured to detectsignals from a stylus associated with the electronic device 1200. Insome embodiments, the processing unit 1208 includes: a display enablingunit 1210, a detecting unit 1212, an updating unit 1214, a sending unit1216, and/or a selecting unit 1218.

The processing unit 1208 is configured to enable display of a userinterface at a first display rate (e.g., with display enabling unit1210).

The processing unit 1208 is also configured to, while the user interfaceis displayed, detect, at a first detection rate that is greater than thefirst display rate, movement of a touch input at a sequence of locationson the touch-sensitive surface unit 1204 (e.g., with detecting unit1212).

The processing unit 1208 is further configured to, at each of a sequenceof update times, update the user interface from a respective currentstate to a respective next state in accordance with a selected subset ofthe sequence of locations of the touch input (e.g., with updating unit1214), each selected subset of the sequence of locations comprising aplurality of locations of the touch input.

In some embodiments, the processing unit 1208 is configured to send to afirst software application a message having information that includesthe selected subset of the sequence of locations (e.g., with sendingunit 1216), and the first software application updates the userinterface in accordance with the information in the message.

In some embodiments, the message also includes information identifyingone or more of: intensity of the touch input at the selected subset ofthe sequence of locations; and a type of the touch input detected at theselected subset of the sequence of locations.

In some embodiments, a last detected location in each selected subset isdetected at least a predefined time interval prior to a next updatetime.

In some embodiments, the processing unit 1208 is configured to select arespective touch location in the selected subset of the sequence oflocations of the touch input as a representative touch location (e.g.,with selecting unit 1218).

In some embodiments, the respective touch location is selected as therepresentative touch location in accordance with touch-processingcriteria for the first application that indicate an amount of timeneeded by the first application to update the user interface.

In some embodiments, updating the user interface by the firstapplication includes transmitting the selected subset of the sequence oflocations of the touch input to the first application along with anindication of which location is the representative touch location.

In some embodiments, the selected subset of the sequence of locationsincludes one or more interstitial locations that correspond to touchlocations between a prior representative touch location and therepresentative touch location.

In some embodiments, the processing unit 1208 is configured to, for eachupdate time in the sequence of update times, select a plurality oflocations of the touch input to use for updating the user interface(e.g., with selecting unit 1218), wherein the selected locations arelocations of the touch input detected after a last selection oflocations to use for updating the user interface.

In some embodiments, the selected plurality of locations of the touchinput includes one or more predicted interstitial locations.

In some embodiments, the processing unit 1208 is configured to, for eachupdate time in the sequence of update times, select a plurality oflocations of the touch input to use for updating the user interface(e.g., with selecting unit 1218), wherein the selected locations arelocations of the touch input detected after detecting locations of thetouch input last selected for updating the user interface.

In some embodiments, the selected locations include all of the locationsof the touch input detected after detecting locations of the touch inputlast selected for updating the user interface.

In some embodiments, the selected locations include only one of thelocations of the touch input detected after detecting locations of thetouch input last selected for updating the user interface.

In some embodiments, the processing unit 1208 is configured to updatethe user interface from a first state to a second state in accordancewith a first subset of the sequence of locations of the touch input(e.g., with updating unit 1214); and, subsequent to updating the userinterface from the first state to the second state, update the userinterface from the second state to a third state in accordance with asecond subset of the sequence of locations of the touch input.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 1300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, the electronic device 1300 includes a display unit1302 configured to display a user interface, a touch-sensitive surfaceunit 1304 configured to receive contacts, and a processing unit 1308coupled with the display unit 1302 and the touch-sensitive surface unit1304. In some embodiments, the electronic device includes one or moresensor units 1306 configured to detect inputs, and the processing unit1308 is also coupled with the one or more sensor units 1306. In someembodiments, the one or more sensor units 1306 include one or moresensors configured to detect intensity of contacts with thetouch-sensitive surface unit 1304. In some embodiments, the one or moresensor units 1306 include one or more sensors configured to detectsignals from a stylus associated with the electronic device 1300. Insome embodiments, the processing unit 1308 includes: a display enablingunit 1310, a detecting unit 1312, a selecting unit 1314, a sending unit1316, an updating unit 1318, a forgoing unit 1320, a determining unit1322, a monitoring unit 1324, and/or a setting unit 1326.

The processing unit 1308 is configured to enable display of a userinterface of a first software application that is updated at a firstdisplay rate (e.g., with display enabling unit 1310).

The processing unit 1308 is also configured to, while a first frame ofthe user interface in accordance with the first display rate isdisplayed: detect respective movement of a touch input across thetouch-sensitive surface unit 1304 (e.g., with detecting unit 1312); and,at an application-independent touch processing module: select arespective touch location of the touch input that was detected duringthe respective movement to identify as a representative touch locationfor the respective movement based on touch-processing criteria for thefirst software application (e.g., with selecting unit 1314); and send toan application-specific portion of the first software application, whichis distinct from the touch processing module, touch location informationfor the touch input that identifies the respective touch location as therepresentative touch location for the respective movement (e.g., withsending unit 1316).

The processing unit 1308 is further configured to, at the first softwareapplication, update the user interface in accordance with the touchlocation information (e.g., with updating unit 1318).

In some embodiments, the processing unit 1308 is configured to send(e.g., with sending unit 1316) the touch location information with afirst portion of the first software application, comprising anapplication-independent sub-module, and update the user interface with asecond portion of the software application that comprises anapplication-specific sub-module (e.g., with updating unit 1318).

In some embodiments, the movement of the touch input is detected duringa respective touch-detection frame; an updated user interface of thefirst application, based on the movement of the touch input, isgenerated during a respective touch-processing frame; and the updateduser interface is displayed on the display for the duration of arespective display frame that occurs after the respectivetouch-processing frame.

In some embodiments, the processing unit 1308 is configured to, duringthe respective touch-processing frame, enable display of a userinterface for the first application that was generated during a priortouch-processing frame (e.g., with display enabling unit 1310).

In some embodiments, the processing unit 1308 is configured to, duringthe respective display frame, detect subsequent movement of the touchinput across the touch-sensitive surface unit 1304 and send to the firstsoftware application touch location information for the subsequentmovement of the touch input (e.g., with detecting unit 1312).

In some embodiments, selecting the respective touch location as therepresentative touch location includes: detecting a first touch locationof the touch input during the touch-detection frame, and in response todetecting the first location: in accordance with a determination thatthe first touch location meets the touch-processing criteria for thefirst application, selecting the first touch location as therepresentative touch location for the respective movement of the touchinput; and, in accordance with a determination that the first touchlocation does not meet the touch-processing criteria for the firstapplication, forgoing selecting the first touch location as therepresentative touch location for the respective movement of the touchinput.

In some embodiments, selecting the respective touch location as therepresentative touch location includes: detecting a second touchlocation of the touch input during the touch-detection frame, and inresponse to detecting the second location, in accordance with adetermination that the second touch location meets the touch-processingcriteria for the first application, selecting the second touch locationas the representative touch location for the respective movement of thetouch input.

In some embodiments, the processing unit 1308 is configured to, inaccordance with a determination that the second touch location does notmeet touch-processing criteria for the first application, forgo (e.g.,with forgoing unit 1320) selecting the second touch location as therepresentative touch location for the respective movement of the touchinput.

In some embodiments, the processing unit 1308 is configured to, at theapplication-independent touch processing module: determine (e.g., withdetermining unit 1322) a timing of sending the one or more selectedlocations to the first software application; and send (e.g., withsending unit 1316) the one or more selected locations to the firstsoftware application in accordance with the determined timing.

In some embodiments, the processing unit 1308 is configured to monitorstatus of the first software application (e.g., with monitoring unit1324), wherein the timing is determined in accordance with the status ofthe first software application.

In some embodiments, the processing unit 1308 is configured to:determine (e.g., with determining unit 1322) a processing margin time;at each of a sequence of communication times, each of which precedes adisplay update time in a sequence of display update times by at leastthe determined processing margin time, send (e.g., with sending unit1316), from the touch processing module to the first softwareapplication, a set of locations that includes one or more selectedlocations of the touch input during a preceding time period; and, at thefirst software application, update (e.g., with updating unit 1318) thefirst user interface in time for display at the sequence of displayupdate times in accordance with the set of locations sent by the touchprocessing module at the sequence of communication times.

In some embodiments, determining the processing margin time includessetting (e.g., with setting unit 1326) the processing margin time to aninitial value and then determining an updated processing margin time inaccordance with one or more measurements of performance of the firstsoftware application.

In some embodiments, the processing margin time is determined inaccordance with a longest processing time by the first softwareapplication while processing each of a plurality of sets of touch inputlocations.

In some embodiments, the locations of the touch input included in theset of locations sent at each communication time correspond to aplurality of detected locations of the touch input between successivecommunication times in the sequence of communication times.

In some embodiments, the processing unit 1308 is configured to send(e.g., with sending unit 1316) to the first software applicationpredicted touch location information for the touch input that identifiesone or more predicted touch locations for the respective movement.

In some embodiments, the processing unit 1308 is configured to send(e.g., with sending unit 1316) the touch location information for thetouch input to a plurality of software applications, including the firstsoftware application.

In some embodiments, the processing unit 1308 is configured to: send(e.g., with sending unit 1316) to the first software application thetouch location information for the touch input in accordance with adetermination that the first software application is configured toreceive the touch location information; and send (e.g., with sendingunit 1316) to a second software application that is distinct from thefirst software application subsequent touch location information for thetouch input in accordance with a determination that the second softwareapplication is configured to receive the subsequent touch locationinformation.

In accordance with some embodiments, FIG. 14 shows a functional blockdiagram of an electronic device 1400 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 14 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 14, the electronic device 1400 includes a display unit1402 configured to display a user interface, a touch-sensitive surfaceunit 1404 configured to receive contacts, and a processing unit 1408coupled with the display unit 1402 and the touch-sensitive surface unit1404. In some embodiments, the electronic device includes one or moresensor units 1406 configured to detect inputs, and the processing unit1408 is also coupled with the one or more sensor units 1406. In someembodiments, the one or more sensor units 1406 include one or moresensors configured to detect intensity of contacts with thetouch-sensitive surface unit 1404. In some embodiments, the one or moresensor units 1406 include one or more sensors configured to detectsignals from a stylus associated with the electronic device 1400. Insome embodiments, the processing unit 1408 includes: a display enablingunit 1410, a detecting unit 1412, a predicting unit 1414, an updatingunit 1416, a sending unit 1418, and/or a comparing unit 1420.

The processing unit 1408 is configured to enable display of a userinterface at a first display rate (e.g., with display enabling unit1410).

The processing unit 1408 is also configured to, while displaying theuser interface in accordance with the first display rate: detect (e.g.,with detecting unit 1412) movement of a touch input, including detectingthe touch input at a first set of sequential locations on thetouch-sensitive surface unit, wherein the first set of sequentiallocations includes a plurality of locations on the touch-sensitivesurface unit; and predict (e.g., with predicting unit 1412) for thetouch input a first set of one or more predicted locations on thetouch-sensitive surface unit based on multiple locations in the firstset of sequential locations.

The processing unit 1408 is further configured to update (e.g., withupdating unit 1416) the user interface in accordance with the first setof one or more predicted locations of the touch input on thetouch-sensitive surface unit.

In some embodiments, the movement of the touch input is detected at afirst detection rate that is higher than the first display rate.

In some embodiments, the processing unit 1408 is configured to, at anapplication-independent touch processing module: predict (e.g., withpredicting unit 1414) for the touch input the first set of one or morepredicted locations on the touch-sensitive surface unit 1404; and send(e.g., with sending unit 1418) to an application-specific portion of thefirst software application the first set of one or more predictedlocations of the touch input on the touch-sensitive surface unit 1404.The processing unit 1408 is also configured to, at the first softwareapplication, update (e.g., with updating unit 1416) the user interfacein accordance with the first set of one or more predicted locations ofthe touch input on the touch-sensitive surface unit 1404.

In some embodiments, the processing unit 1408 is configured to,subsequent to detecting the touch input at the first set of sequentiallocations on the touch-sensitive surface unit 1404: detect (e.g., withdetecting unit 1412) the touch input at a second set of sequentiallocations on the touch-sensitive surface unit 1404; compare (e.g., withcomparing unit 1420) the second set of sequential locations of the touchinput on the touch-sensitive surface unit 1404 with the first set of oneor more predicted locations of the touch input on the touch-sensitivesurface unit 1404; and, in accordance with a determination that adifference between the first set of one or more predicted locations ofthe touch input on the touch-sensitive surface unit 1404 and the secondset of sequential locations of the touch input on the touch-sensitivesurface unit 1404 satisfies predefined criteria, update (e.g., withupdating unit 1416) the user interface in accordance with the second setof sequential locations of the touch input on the touch-sensitivesurface unit 1404.

In some embodiments, the processing unit 1408 is configured to: predict(e.g., with predicting unit 1414) for the touch input a second set ofone or more locations on the touch-sensitive surface unit 1404; andupdate (e.g., with updating unit 1416) the user interface in accordancewith the second set of sequential locations on the touch-sensitivesurface unit 1404 and the second set of one or more predicted locationsof the touch input on the touch-sensitive surface unit 1404.

In some embodiments, a portion of the user interface that is updated inaccordance with one or more predicted locations is visuallydistinguished from a portion of the user interface that is updated inaccordance with one or more detected locations.

In some embodiments, the movement of the touch input is detected duringa respective touch-detection frame; an updated user interface, based onthe movement of the touch input, is generated during a respectivetouch-processing frame; and the updated user interface is displayed onthe display for the duration of a respective display frame that occursafter the respective touch-processing frame.

In some embodiments, the one or more predicted locations of the touchinput on the touch-sensitive surface unit 1404 are predicted based atleast in part on multiple representative touch locations of the touchinput on the touch-sensitive surface unit 1404.

In some embodiments, the one or more predicted locations of the touchinput on the touch-sensitive surface unit 1404 are predicted based onmultiple representative touch locations of the touch input on thetouch-sensitive surface unit 1404 and one or more interstitial locationsof the touch input on the touch-sensitive surface unit 1404.

In some embodiments, each of the one or more predicted locations is apredicted representative touch location.

In some embodiments, the one or more predicted locations include one ormore predicted interstitial touch locations of the touch input on thetouch-sensitive surface unit 1404.

In some embodiments, a number of predicted locations in the first set ofone or more predicted locations of the touch input is determined inaccordance with one or more confidence values associated with the one ormore predicted locations.

In some embodiments, a number of predicted locations in the first set ofone or more predicted locations of the touch input is determined inaccordance with one or more confidence values associated with themultiple locations in the first set of sequential locations.

In some embodiments, the one or more confidence values associated withthe multiple locations in the first set of sequential locations arebased at least in part on errors in fitting the multiple locations inthe first set of sequential locations to a predefined constraint.

In some embodiments, the one or more confidence values associated withthe multiple locations in the first set of sequential locations arebased at least in part on speed of the movement of the touch input.

In some embodiments, the electronic device includes one or more sensorsto detect intensity of touch inputs on the touch-sensitive surface unit1404. The processing unit 1408 is configured to: predict (e.g., withpredicting unit 1414) intensity of the touch input at a plurality oflocations on the touch-sensitive surface unit 1404; and update (e.g.,with updating unit 1416) the user interface in accordance with thepredicted intensity of the touch input.

In some embodiments, the processing unit 1408 is configured to: predict(e.g., with predicting unit 1414) tilt and/or orientation of the touchinput at a plurality of locations on the touch-sensitive surface unit1404; and update (e.g., with updating unit 1416) the user interface inaccordance with the predicted tilt and/or orientation of the touchinput.

In accordance with some embodiments, FIG. 15 shows a functional blockdiagram of an electronic device 1500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 15 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 15, the electronic device 1500 includes a display unit1502 configured to display a user interface, a touch-sensitive surfaceunit 1504 configured to receive contacts, and a processing unit 1510coupled with the display unit 1502 and the touch-sensitive surface unit1504. In some embodiments, the electronic device includes one or moresensor units 1506 configured to detect inputs, and the processing unit1510 is also coupled with the one or more sensor units 1506. In someembodiments, the one or more sensor units 1506 include one or moresensors configured to detect intensity of contacts with thetouch-sensitive surface unit 1504. In some embodiments, the one or moresensor units 1506 include one or more sensors configured to detectsignals from a stylus associated with the electronic device 1500. Insome embodiments, the processing unit 1508 includes: a display enablingunit 1510, a detecting unit 1512, a sending unit 1514, a processing unit1516, and/or a posting unit 1518.

The processing unit 1508 is configured to enable display of a userinterface of a first software application that is updated at a firstdisplay rate (e.g., with display enabling unit 1510); and detect (e.g.,with detecting unit 1512) respective movement of a touch input acrossthe touch-sensitive surface unit 1504 at a first detection rate that ishigher than the first display rate.

The processing unit 1508 is also configured to, at anapplication-independent touch processing module, send (e.g., withsending unit 1514) to an application-specific portion of the firstsoftware application touch location information for the touch input thatidentifies: one or more predicted locations of the touch input on thetouch-sensitive surface unit 1504; and one or more predicted intensityvalues of the touch input at one or more intensity locations of thetouch input on the touch-sensitive surface unit 1504, the one or moreintensity locations comprising at least a subset of the one or morepredicted locations.

The processing unit 1508 is further configured to, at the first softwareapplication, process (e.g., with processing unit 1516) the touchlocation information.

In some embodiments, the touch location information includes arespective touch identifier for each predicted location in the one ormore predicted locations of the touch input on the touch-sensitivesurface unit 1504.

In some embodiments, the touch location information also identifies: aplurality of detected locations of the touch input on thetouch-sensitive surface unit 1504; and a plurality of intensity valuesof the touch input at a plurality of intensity locations on thetouch-sensitive surface unit 1504.

In some embodiments, the plurality of intensity locations on thetouch-sensitive surface unit 1504 is the plurality of detectedlocations.

In some embodiments, the touch location information includes one or moretouch identifiers for the plurality of detected locations.

In some embodiments, the touch location information also identifiespredicted tilt and/or orientation of the touch input.

In some embodiments, the touch location information also identifies atype of the touch input.

In some embodiments, sending to the application-specific portion of thefirst software application touch location information for the touchinput includes posting (e.g., with posting unit 1518) the touch locationinformation for the touch input.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 8A-8B, 9A-9D,10A-10C, and 11 are, optionally, implemented by components depicted inFIGS. 1A-1B or FIGS. 12-15. For example, detection operation 804,message sending operation 808, and updating operation 814 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 146-1. A respective eventrecognizer 180 of application 146-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at an electronic devicewith a touch-sensitive surface and display: displaying a user interfaceof a first software application that is updated at a first display rate;while displaying a first frame of the user interface in accordance withthe first display rate: detecting respective movement of a touch inputacross the touch-sensitive surface; at an application-independent touchprocessing module: selecting a respective touch location of the touchinput that was detected during the respective movement to identify as arepresentative touch location for the respective movement based ontouch-processing criteria for the first software application; andsending to an application-specific portion of the first softwareapplication, which is distinct from the touch processing module, touchlocation information for the touch input that identifies the respectivetouch location as the representative touch location for the respectivemovement; and, at the first software application, updating the userinterface in accordance with the touch location information.
 2. Themethod of claim 1, including sending the touch location information witha first portion of the first software application, comprising anapplication-independent sub-module, and updating the user interface witha second portion of the software application that comprises anapplication-specific sub-module.
 3. The method of claim 1, wherein: themovement of the touch input is detected during a respectivetouch-detection frame; an updated user interface of the firstapplication, based on the movement of the touch input, is generatedduring a respective touch-processing frame; and the updated userinterface is displayed on the display for the duration of a respectivedisplay frame that occurs after the respective touch-processing frame.4. The method of claim 3, including, during the respectivetouch-processing frame, displaying a user interface for the firstapplication that was generated during a prior touch-processing frame. 5.The method of claim 3, including, during the respective display frame,detecting subsequent movement of the touch input across thetouch-sensitive surface and sending to the first software applicationtouch location information for the subsequent movement of the touchinput.
 6. The method of claim 1, wherein selecting the respective touchlocation as the representative touch location includes: detecting afirst touch location of the touch input during a touch-detection framethat precedes a respective display update time, and in response todetecting the first location: in accordance with a determination thatthe first touch location meets the touch-processing criteria for thefirst application, selecting the first touch location as therepresentative touch location for the respective movement of the touchinput; and, in accordance with a determination that the first touchlocation does not meet the touch-processing criteria for the firstapplication, forgoing selecting the first touch location as therepresentative touch location for the respective movement of the touchinput.
 7. The method of claim 6, wherein selecting the respective touchlocation as the representative touch location includes: detecting asecond touch location of the touch input during the touch-detectionframe, and in response to detecting the second location: in accordancewith a determination that the second touch location meets thetouch-processing criteria for the first application, selecting thesecond touch location as the representative touch location for therespective movement of the touch input.
 8. The method of claim 7,including: in accordance with a determination that the second touchlocation does not meet touch-processing criteria for the firstapplication, forgoing selecting the second touch location as therepresentative touch location for the respective movement of the touchinput.
 9. The method of claim 1, including: at theapplication-independent touch processing module: determining a timing ofsending the one or more selected locations to the first softwareapplication; and sending the one or more selected locations to the firstsoftware application in accordance with the determined timing.
 10. Themethod of claim 9, including: monitoring status of the first softwareapplication, wherein the timing is determined in accordance with thestatus of the first software application.
 11. The method of claim 1,including: determining a processing margin time; at each of a sequenceof communication times, each of which precedes a display update time ina sequence of display update times by at least the determined processingmargin time, sending, from the touch processing module to the firstsoftware application, a set of locations that includes one or moreselected locations of the touch input during a preceding time period;and, at the first software application, updating the first userinterface in time for display at the sequence of display update times inaccordance with the set of locations sent by the touch processing moduleat the sequence of communication times.
 12. The method of claim 11,wherein determining the processing margin time includes setting theprocessing margin time to an initial value and then determining anupdated processing margin time in accordance with one or moremeasurements of performance of the first software application.
 13. Themethod of claim 11, wherein the processing margin time is determined inaccordance with a longest processing time by the first softwareapplication while processing each of a plurality of sets of touch inputlocations.
 14. The method of claim 11, wherein the locations of thetouch input included in the set of locations sent at each communicationtime correspond to a plurality of detected locations of the touch inputbetween successive communication times in the sequence of communicationtimes.
 15. The method of claim 14, further comprising: sending to thefirst software application predicted touch location information for thetouch input that identifies one or more predicted touch locations forthe respective movement.
 16. The method of claim 1, further comprising:sending the touch location information for the touch input to aplurality of software applications, including the first softwareapplication.
 17. The method of claim 1, including: sending to the firstsoftware application the touch location information for the touch inputin accordance with a determination that the first software applicationis configured to receive the touch location information; and sending toa second software application that is distinct from the first softwareapplication subsequent touch location information for the touch input inaccordance with a determination that the second software application isconfigured to receive the subsequent touch location information.
 18. Anelectronic device, comprising: a display; a touch-sensitive surface; oneor more processors; memory; and one or more programs, wherein the one ormore programs are stored in the memory and configured to be executed bythe one or more processors, the one or more programs includinginstructions for: displaying a user interface of a first softwareapplication that is updated at a first display rate; while displaying afirst frame of the user interface in accordance with the first displayrate: detecting respective movement of a touch input across thetouch-sensitive surface; and, at an application-independent touchprocessing module: selecting a respective touch location of the touchinput that was detected during the respective movement to identify as arepresentative touch location for the respective movement based ontouch-processing criteria for the first software application; andsending to an application-specific portion of the first softwareapplication, which is distinct from the touch processing module, touchlocation information for the touch input that identifies the respectivetouch location as the representative touch location for the respectivemovement; and, at the first software application, updating the userinterface in accordance with the touch location information.
 19. Acomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by anelectronic device with a display and a touch-sensitive surface, causethe device to: display a user interface of a first software applicationthat is updated at a first display rate; while displaying a first frameof the user interface in accordance with the first display rate: detectrespective movement of a touch input across the touch-sensitive surface;and, at an application-independent touch processing module: select arespective touch location of the touch input that was detected duringthe respective movement to identify as a representative touch locationfor the respective movement based on touch-processing criteria for thefirst software application; and send to an application-specific portionof the first software application, which is distinct from the touchprocessing module, touch location information for the touch input thatidentifies the respective touch location as the representative touchlocation for the respective movement; and, at the first softwareapplication, update the user interface in accordance with the touchlocation information.